Getting Started with Integration Workflows
This guide walks you through connecting your first integration and building your first workflow from scratch.
Step 1 — Connect an integration
Before you can use an integration in a workflow, you need to connect it from the Integrations settings page.
- Go to Settings → Integrations
- Find the integration you want (e.g. HubSpot, Klaviyo, Shippo)
- Click Connect
- Enter your API key or OAuth credentials
- Click Save — the connection is tested automatically
Your credentials are encrypted with AES-256 before storage. LaunchStore never stores them in plain text.
You only need to connect an integration once per store. After that, any workflow you build for that store can use it.
Step 2 — Create a new workflow
- Go to Integrations → Workflows
- Click New Workflow
- Give your workflow a name (e.g. "Sync order to HubSpot")
- Click Create
Step 3 — Add a trigger node
The trigger is the store event that starts the workflow.
- On the canvas, click Add Trigger
- Select the event — e.g.
order.created - The trigger node appears on the canvas
Available triggers: order.created, order.fulfilled, order.canceled, order.refunded, customer.created, fulfillment.created
Step 4 — Add an action node
- Click the + handle on the trigger node
- Select the integration and action (e.g. HubSpot → Create Contact)
- Configure the action — map the fields from the event payload to the API call
Example field mapping for HubSpot Create Contact
| HubSpot field | Source |
|---|---|
{{ order.email }} | |
| First name | {{ order.customer.first_name }} |
| Last name | {{ order.customer.last_name }} |
| Phone | {{ order.shipping_address.phone }} |
Step 5 — Chain additional actions (optional)
You can connect multiple action nodes in sequence. For example:
order.created → HubSpot: Create Contact → Klaviyo: Identify Profile → Complete
Each action receives the same trigger payload. You can reference any field from the original event.
Step 6 — Save and activate
- Click Save — the workflow is saved as a Draft
- Click Activate — the workflow is translated into n8n JSON and deployed to the n8n cluster
- Status changes to Active
Once active, every matching store event triggers the workflow automatically.
Step 7 — Watch the first execution
- Place a test order in your store (or use your Medusa admin)
- Go to Integrations → Execution History
- You should see a new execution appear with status COMPLETED within seconds
If the execution shows FAILED, check the execution detail to see the error from n8n.
Managing workflows
| Action | What it does |
|---|---|
| Deactivate | Pauses the workflow — no new executions until re-activated |
| Edit | Modify nodes (workflow must be deactivated first) |
| Delete | Archives the workflow permanently |
You need to deactivate a workflow before editing it. LaunchStore re-deploys it to n8n on the next activation.