Importing a workflow

Every purchase includes a workflow.json file. In n8n, go to Workflows → Add Workflow → Import from File and select it (self-hosted n8n and n8n Cloud both support this the same way). The full node canvas — triggers, logic, and every integration — appears exactly as designed. Nothing needs to be built from scratch.

Using Make instead of n8n? Every setup guide includes notes on adapting the flow.

Connecting credentials

Each node that talks to an external service (Gmail, Slack, Google Sheets, your AI provider, etc.) needs its own credential, connected once inside n8n:

1. Click the node.
2. Under Credential to connect with, choose “Create New”.
3. Follow that service’s OAuth flow (Google, Slack, Notion) or paste an API key (OpenAI, Twilio, HubSpot).

Credentials live entirely inside your own n8n account — see the Trust Center for exactly what does and doesn’t pass through Flowmanic.

Configuring nodes

Workflows ship with clearly-marked placeholders — YOUR_GOOGLE_SHEET_ID, YOUR_SLACK_CHANNEL_ID, and similar. Each product’s setup guide lists every placeholder that needs a real value and exactly where to find it (e.g. a Google Sheet’s ID is the long code in its URL). Everything else — the logic, the field mappings, the message text — is already built and rarely needs changes unless you want to customize it.

Testing before you activate

Before switching a workflow to Active, use n8n’s “Execute Workflow” / “Listen for test event” mode to trigger it manually once and confirm every node runs cleanly. For webhook-triggered workflows, use the “Test URL” shown on the trigger node — it only works while the editor is open, which is exactly what you want for a dry run.

Common errors

• Webhook never triggers. Confirm the workflow is Active and pointed at the “Production URL”, not the “Test URL” — the test URL only listens while the n8n editor is open.
• Google Sheets trigger feels slow or misses changes. Sheets triggers poll on an interval (commonly every minute) — this is normal, not a bug, and only fires for genuinely new/changed rows, not a manual re-check.
• A node errors with a 401/403. The credential attached to that node is either missing scopes or has expired — reconnect it via OAuth or regenerate the API key.
• AI-powered node returns an error. Check the AI API credential first — a malformed Authorization header or an exhausted quota are the two most common causes.

How updates work

If a template is updated (a fixed node mapping, a compatibility update after an integration changes its API), All-Access and System buyers receive the new version by email at no extra charge. Individual template purchases are for that version at time of purchase — check the specific product page for anything version-specific.

FAQ

For general questions (do I need coding experience, what happens when APIs change, can I use these for client work), see the FAQ section on the homepage or the specific product page you’re asking about — every automation has its own FAQ covering questions specific to that workflow.