Migrate Zapier Zaps to n8n (Workflow Automation)

Hey there, Darian Vance here. As a Senior DevOps Engineer at TechResolve, I’m always looking for ways to streamline our processes, cut down on SaaS sprawl, and get more control over our data pipelines. A few years back, I audited our automation stack and realized we were spending a small fortune on Zapier across multiple teams. The “per-task” pricing was becoming unpredictable. Migrating our core workflows to a self-hosted n8n instance wasn’t just about saving money; it was about gaining full ownership and extensibility. It gave us the power to build more complex, robust automations without worrying about a bill for every run. Today, I’m going to walk you through how to make that same move.

Prerequisites

Before we dive in, let’s make sure you have everything ready. This isn’t a “from scratch” setup guide, I’m assuming you’ve got the basics covered.

• An active n8n instance, either on n8n.cloud or self-hosted.
• Administrator access to your organization’s Zapier account.
• A clear understanding of the Zap you want to migrate. We’ll deconstruct it together.
• A working knowledge of APIs and JSON data structures. You don’t need to be a guru, but you should be comfortable reading a JSON object.

The Step-by-Step Migration Guide

The best way to learn is by doing. Let’s take a common business workflow as our example: When a new customer is created in Stripe, add them to a specific Mailchimp audience and send a welcome message to a Slack channel.

Step 1: Deconstruct the Zap

First, open your Zap in Zapier and map it out. Don’t just look at it—document it. Identify the key components:

• Trigger: Stripe – “New Customer”
• Action 1: Filter – “Only continue if… Customer Email is not empty”
• Action 2: Mailchimp – “Add/Update Subscriber”
• Action 3: Slack – “Send Channel Message”

The most important part here is to note which data fields are passed from one step to the next. For example, you’re likely passing `Customer Email` and `Customer Name` from Stripe to Mailchimp, and `Customer Name` to Slack.

Step 2: Rebuild the Trigger in n8n

In your n8n canvas, click the ‘+’ button to add your first node. Search for “Stripe” and select the “Stripe Trigger” node.

1. Authentication: The first thing n8n will ask for is credentials. This is one of my favorite parts of n8n. You create the credential once (e.g., “My Production Stripe Key”) and can reuse it in any Stripe node across all your workflows. Add your Stripe API key here.
2. Configuration: In the ‘Resource’ dropdown, select ‘Customer’. In the ‘Event’ dropdown, select ‘Created’.
3. Test: Use the ‘Fetch test event’ button. n8n will pull in a recent ‘New Customer’ event from your Stripe account. This gives you live, structured data to work with for the rest of the build, which is a massive time-saver compared to Zapier’s sometimes abstract sample data.

Step 3: Add Logic and Actions

Now we just chain the actions together, recreating our Zap’s logic.

The Filter: In Zapier, this was a specific “Filter” step. In n8n, we often use the “IF” node for this. Add an IF node connected to the Stripe trigger. Set the condition to check if the email from the Stripe node exists. The expression might look something like this in the ‘Value 1’ field: {{ $json["body"]["data"]["object"]["email"] }}. Set the operation to ‘Is Not Empty’. The IF node creates two outputs: true and false. We’ll build the rest of our workflow off the ‘true’ output.

The Mailchimp Action: Drag from the ‘true’ output of the IF node and add a “Mailchimp” node.

1. Authenticate your Mailchimp account, just like you did with Stripe.
2. Select your Audience list from the dropdown.
3. Now, map the data. In the ‘Email’ field, click the ‘Add Expression’ button and select the email from the Stripe Trigger node’s output. It’ll look something like {{ $json["body"]["data"]["object"]["email"] }}. Do the same for first name, last name, etc.

Pro Tip: n8n’s expression editor is incredibly powerful. You’re not just mapping fields; you can write JavaScript right in the expression to format dates, concatenate strings, or perform calculations. For instance, to format a name, you could use an expression like: Welcome, {{ $json.body.data.object.name.split(' ')[0] }}! to grab just the first name.

The Slack Action: Finally, add a “Slack” node. Connect it to the Mailchimp node.

1. Authenticate your Slack account.
2. Choose the channel you want to post to.
3. Craft your message using expressions. Your ‘Text’ field could be: `New customer signed up! Welcome {{ $(‘Stripe Trigger’).item.json.body.data.object.name }} ({{ $(‘Stripe Trigger’).item.json.body.data.object.email }}). They’ve been added to our newsletter.`

Step 4: Handling Complex Transformations (The Code Node)

Sometimes, you need to do something more complex than simple data mapping. This is where n8n’s Code node really shines. Let’s say we need to format the customer data into a specific JSON structure for an internal API call.

Add a ‘Code’ node. It runs JavaScript (Node.js) by default. Here’s a simple example of how you might transform incoming data.

const stripeData = $input.item.json;

// Let's assume the Stripe object is nested
const stripeCustomer = stripeData.body.data.object;

const formattedPayload = {
  userInfo: {
    fullName: stripeCustomer.name,
    contactEmail: stripeCustomer.email,
    source: 'n8n-migration-workflow'
  },
  metadata: {
    stripeId: stripeCustomer.id,
    createdAt: new Date().toISOString()
  }
};

// n8n expects an array of objects to be returned.
// Each object becomes an "item" for the next node.
return [{ json: formattedPayload }];

This code block takes the incoming item, reshapes it into a new `formattedPayload` object, and returns it. The next node in your workflow can now directly access `userInfo.fullName` or `metadata.stripeId`. This level of control is something I find essential for serious production workflows.

Common Pitfalls (Where I Usually Mess Up)

• Forgetting Item Structures: n8n processes data as a series of “items” in an array. Zapier hides this. A node can output multiple items, and the next node will run once for each. This is powerful, but if you’re not expecting it, it can be confusing. Always check the output of a node to see if you’re getting one item or many.
• Expression Syntax Errors: I still mess this up. Forgetting a curly brace or referencing a node name incorrectly (`{{ $(‘My Node Name’).item.json.field }}`). The best advice I have is to use the expression editor’s variable selector on the left—it builds the path for you. Don’t try to type it all from memory.
• Credential Permissions: You create a credential for, say, Google Sheets, but you only give it read access. Then your “Update Row” node fails. It’s almost always a permissions issue. When creating credentials, ensure they have the scopes required for all the actions you intend to perform.

Conclusion

Migrating from Zapier to n8n is less of a direct translation and more of a strategic upgrade. You’re trading the guided, sometimes restrictive, nature of Zapier for the raw power and flexibility of n8n. The initial learning curve is slightly steeper, but the payoff in control, cost-effectiveness, and capability is enormous. Start with one or two simple Zaps, get comfortable with the n8n interface and data flow, and you’ll be building powerful, custom automations in no time. Good luck, and feel free to reach out if you get stuck.

Darian Vance

Lead Cloud Architect & DevOps Strategist

With over 12 years in system architecture and automation, Darian specializes in simplifying complex cloud infrastructures. An advocate for open-source solutions, he founded TechResolve to provide engineers with actionable, battle-tested troubleshooting guides and robust software alternatives.

🤖 Frequently Asked Questions