Integrationworkflows.
Connect your store to HubSpot, Klaviyo, Mailchimp, Pipedrive, Shippo, Stripe, and 20+ tools. Triggered by real Medusa events. Executed by n8n. No code. No Zapier.
Workflow canvas · order → HubSpot + Klaviyo
Trigger
order.created
HubSpot
Create Contact
Klaviyo
Identify Profile
Complete
Execution finished
1,247
Executions
99.3%
Success rate
1.2s
Avg duration
Who uses this
DTC owner syncing orders to HubSpot CRM
“Every new order meant manually adding the customer to HubSpot. I was 2 weeks behind on CRM data and had no idea which customers were about to churn.”
Set up an order.created → HubSpot Create Contact workflow in under 10 minutes. CRM is always in sync, no manual entry, and my sales team can see every order the moment it lands.
Agency managing Klaviyo flows for multiple stores
“Each client needed manual CSV exports to sync new customers into Klaviyo. It was error-prone, delayed by days, and killed hours of my team's time every week.”
One integration workflow per store: customer.created → Klaviyo Identify Profile. All stores stay in sync automatically. Client Klaviyo lists are always clean and current.
Store owner auto-creating Shippo labels
“Creating shipping labels for every order was a manual step in Shippo's dashboard. During peak season I was hours behind on fulfillment.”
order.fulfilled → Shippo Create Label workflow runs every time. Labels are generated automatically the moment we mark an order fulfilled. Zero manual steps.
8 integrations. 14 actions.
Every action maps directly to a native n8n node — credentials stay in n8n, execution happens in n8n.
- Create Contact
- Create Deal
- Create Ticket
- Identify Profile
- Track Event
- Add Subscriber
- Update Subscriber
- Create Contact
- Create Deal
- Send Email
- Create Customer
- Create Shipment
- Create Label
- Create Payment
6 Medusa event triggers
Every trigger fires in real time when the event happens in your store — not on a polling schedule. Medusa subscribers bridge events to the LaunchStore backend via HMAC-authenticated webhooks, where WorkflowEventService routes them to matching active workflows.
order.created
New order placed in your store
order.fulfilled
Fulfillment created for an order
order.canceled
Order cancelled by customer or admin
order.refunded
Full or partial refund issued
customer.created
New customer account created
fulfillment.created
Shipment tracking generated
How the execution pipeline works
- 1
Connect your integration
Go to Integrations → select HubSpot, Klaviyo, Shippo, etc. → enter your API key. Credentials are AES-256 encrypted per-store per-integration before storage.
- 2
Build the workflow on the canvas
Drop a Trigger node, add one or more action nodes (HubSpot Create Contact, Klaviyo Identify Profile, etc.), connect them, and save. The React Flow canvas auto-validates the graph.
- 3
Activate — workflow is pushed to n8n
Clicking Activate translates your workflow graph into n8n's JSON format via WorkflowTranslatorService, creates it in the internal n8n cluster, activates it, and stores the n8nWorkflowId.
- 4
Medusa event fires → BullMQ → n8n
When an order is placed, the Medusa subscriber calls the LaunchStore webhook. WorkflowEventService finds matching active workflows and queues a BullMQ job. WorkflowExecutionProcessor picks it up (concurrency 5) and calls N8nService.executeWorkflow().
- 5
n8n executes — status synced back
n8n runs the full workflow using its native nodes (HubSpot, Klaviyo, etc.) with the credentials you provided. The execution result (success or failure, n8nExecutionId) is written back to integration_executions. The dashboard shows the result in real time via WebSocket.
Enterprise-grade reliability
The infrastructure quality features Zapier and Make charge extra for — all included.
n8n execution engine
Every workflow runs on a dedicated n8n cluster — battle-tested at enterprise scale, with built-in retry logic, error handling, and execution history. You get reliability without managing the infrastructure.
AES-256 encrypted credentials
Your HubSpot, Klaviyo, and Stripe API keys are encrypted before storage using a per-store per-integration key. Never logged, never stored in plain text. Rotate keys at any time from settings.
Backpressure & rate limiting
Per-store concurrency limits (100 running, 1,000 queued) prevent runaway executions from affecting other stores. Events that exceed capacity are dropped cleanly with a warning log — never silently lost.
Real-time WebSocket status
The dashboard shows execution started and completed events via WebSocket — no polling. See your workflow fire and complete in real time as Medusa events land.
How we compare
| Feature | LaunchStore | Zapier | Make | Shopify Flow |
|---|---|---|---|---|
| Visual workflow builder | ✓ | ✓ | ✓ | Plus only ($2k/mo) |
| Triggered by real store events | ✓ | Poll | Poll | ✓ |
| HubSpot / Pipedrive CRM sync | ✓ | ✓ | ✓ | ✗ |
| Klaviyo / Mailchimp subscriber sync | ✓ | ✓ | ✓ | ✗ |
| Shippo label automation | ✓ | ✓ | ✓ | ✗ |
| Encrypted credential storage | ✓ | ✓ | ✓ | N/A |
| Execution history & retry | ✓ | ✓ | ✓ | Limited |
| Real-time WebSocket status | ✓ | ✗ | ✗ | ✗ |
| Backpressure / rate limiting | ✓ | ✗ | ✗ | ✗ |
| Included in base plan | ✓ | ✗ | ✗ | ✗ |
| Starting price | From $9/mo | $20+/mo extra | $9+/mo extra | $2,000+/mo (Plus) |
Common questions
Which integrations are supported?
HubSpot (contacts, deals, tickets), Pipedrive (contacts, deals), Mailchimp (add/update subscribers), Klaviyo (identify profile, track event), SendGrid (send email), Stripe (create customer), PayPal (payment), and Shippo (create shipment, create label). New integrations are added regularly.
Are my API keys stored securely?
All credentials are encrypted with AES-256 before storage using a per-store per-integration key. They are never stored in plain text, never logged, and only decrypted at execution time inside the n8n worker.
What happens when an execution fails?
Failed executions are recorded with FAILED status and the n8n execution ID. You can inspect them in the Execution History dashboard and re-trigger as needed. n8n's built-in error handling applies.
How is this different from Visual Automation flows?
Visual Automation handles email sequences — welcome series, abandoned cart, win-back. Integration Workflows connect your store to external CRM, marketing, and shipping tools via n8n. They are completely separate systems with separate tables, queues, and execution engines.
Do I need a separate n8n account?
No. LaunchStore runs its own internal n8n cluster. Workflows are deployed there automatically when you activate them. You only provide your HubSpot/Klaviyo/Stripe API keys via the integrations settings page.
Connect your stack in minutes.
Replace Zapier and Make. Keep your HubSpot, Klaviyo, and Shippo. No per-task fees. Included in every LaunchStore plan from $9/mo.
No credit card required · 14-day free trial · Cancel anytime