launch policy

Support

Where to get help with account access, billing, workflow errors, and launch feedback.

Contact

Email contact@finkmesh.com from the address on your FinkMesh account. Include the workflow name, run id, or invoice id when relevant.

Workflow quickstart

1

Start from a template

Use a launch template or create a blank workflow with a Manual Trigger.

2

Add actions

Connect APIs and supported app integrations, branch logic, wait, approve, and transform data before publishing.

3

Store secrets safely

Put reusable API keys or bearer tokens in Connections or encrypted workspace variables.

4

Publish when ready

Starter unlocks live webhooks, schedules, and HTTP/API actions. Pro and Scale add native integrations and more room as usage grows.

Plan gates

Free workspaces are for safe manual testing: 100 manual runs per month and 5 live action test runs. Starter is the launch plan for real automations and unlocks HTTP/API actions, webhook triggers, and schedules. Pro and Scale add native integrations, more runs, teammates, workspaces, and throughput when production usage grows.

View plan limits

Troubleshooting

When a run fails
  • Use Runs to inspect the failed step, status code, request summary, and redacted response.
  • If publishing is blocked, check Plan & Billing. Free workspaces can test manually, but live webhooks, schedules, and HTTP/API actions require Starter or higher.
  • If an API rejects your request, confirm the Authorization header, content type, and body format match that provider's docs.
  • If a webhook does not fire, rotate or recreate the endpoint and copy the full URL before closing the reveal panel.

Common paths

Billing changes live in Plan & Billing. Workflow failures can be inspected from Runs, including step inputs, outputs, and errors.

Response priority

Billing and account-access issues are handled first during launch. Product feedback is tracked and prioritized around making workflow automations reliable before expanding native OAuth integrations.