CUSTOMER.IO n8n INTEGRATION: AUTOMATE CUSTOMER.IO WITH N8N

The Create or Update Customer action is your primary tool for managing customer data in Customer.io from external sources. It follows an "upsert" pattern: if a customer with the specified ID exists, it updates their record; if not, it creates a new one. This eliminates the need for separate create and update logic in your workflows.

Key parameters:

• Credential to connect with: Required dropdown to select your Customer.io account credentials.
• Resource: Set to "Customer" to operate on customer records.
• Operation: Set to "Create or Update" for the upsert behavior.
• ID: Required text field where you enter the unique customer identifier. This is how Customer.io determines whether to create or update.
• JSON Parameters: Toggle to enable raw JSON input for complex data structures.
• Additional Fields: Expandable section to add custom attributes like email, name, plan type, or any custom properties.

Use cases: Sync new leads from your website form to Customer.io, update customer attributes when they make a purchase, import customers from a CSV via Google Sheets, or enrich profiles with data from third-party APIs.

The Delete Customer action permanently removes a customer record from Customer.io. Use this for GDPR compliance workflows, cleaning up test data, or removing customers who have explicitly requested data deletion.

Key parameters:

• Credential to connect with: Required dropdown for authentication.
• Resource: Set to "Customer."
• Operation: Set to "Delete."
• ID: Required text field specifying which customer to delete. Double-check this value—deletion is permanent.

Use cases: Automate GDPR "right to be forgotten" requests by connecting a form submission to this action, clean up test customers after QA, or remove duplicate records identified by another workflow.

Track Event lets you record custom events for identified customers in Customer.io. These events can then trigger campaigns, update segments, or be used for analytics. It's essential for tracking in-app behavior, purchases, or any customer action that happens outside Customer.io.

Key parameters:

• Credential to connect with: Required dropdown for account selection.
• Resource: Set to "Event."
• Operation: Set to "Track."
• Customer ID: Required text field identifying which customer performed the event.
• Event Name: Required text field for the event name (e.g., "purchase_completed", "feature_used", "support_ticket_opened").
• JSON Parameters: Toggle to pass additional event properties in JSON format.
• Additional Fields: Add custom event data like product name, amount, or category.

Use cases: Track purchases from your e-commerce platform, record feature usage from your product, log support interactions, or capture any custom action that should influence your marketing automation.

Track Anonymous records events for visitors who haven't been identified yet. This is crucial for tracking pre-signup behavior that you want to associate with a customer profile later. Customer.io will merge these events once the anonymous visitor is identified.

Key parameters:

• Credential to connect with: Required dropdown for authentication.
• Resource: Set to "Event."
• Operation: Set to "Track Anonymous."
• Event Name: Required text field for the event name.
• JSON Parameters: Toggle for passing additional data in JSON format.
• Additional Fields: Add custom properties relevant to the anonymous event.

Use cases: Track page views or content downloads before signup, record pricing page visits for sales intelligence, or capture product demo requests from anonymous visitors.

Get Campaign retrieves detailed information about a specific campaign in your Customer.io account. Use it to check campaign status, pull configuration details, or gather data for reporting workflows.

Key parameters:

• Credential to connect with: Required dropdown for account authentication.
• Resource: Set to "Campaign."
• Operation: Set to "Get."
• Campaign ID: Required text field where you enter the unique identifier of the campaign to retrieve.

Use cases: Build campaign status dashboards, verify campaign configuration before triggering updates, or aggregate campaign data for cross-platform reporting.

Get Many Campaigns retrieves a list of multiple campaigns from your Customer.io account. It's perfect for building overview reports or workflows that need to iterate through all your campaigns.

Key parameters:

• Credential to connect with: Required dropdown for selecting your credentials.
• Resource: Set to "Campaign."
• Operation: Set to "Get Many."

Use cases: Generate weekly campaign performance reports, build a master list of all active campaigns, or create workflows that check multiple campaign statuses in sequence.

Get Metrics pulls performance data for a specific campaign, including delivery rates, open rates, click rates, and conversion metrics. This action is essential for building automated reporting workflows.

Key parameters:

• Credential to connect with: Required dropdown for authentication.
• Resource: Set to "Campaign."
• Operation: Set to "Get Metrics."
• Campaign ID: Required text field specifying which campaign's metrics to retrieve.
• Period: Dropdown to select the time frame for metrics (e.g., "Days").
• JSON Parameters: Toggle for advanced configuration options.
• Additional Fields: Add extra parameters for more specific metric queries.

Use cases: Build daily/weekly campaign performance reports in Google Sheets, trigger alerts when metrics fall below thresholds, or feed campaign data into BI tools for deeper analysis.

Add Customer adds one or more customers to a specific segment in Customer.io. Segments are powerful for targeting campaigns, so dynamically managing segment membership based on external triggers unlocks sophisticated personalization.

Key parameters:

• Credential to connect with: Required dropdown for account selection.
• Resource: Set to "Segment."
• Operation: Set to "Add Customer."
• Segment ID: Required text field for the target segment's unique identifier.
• Customer IDs: Required text field where you list the customer IDs to add (typically comma-separated).

Use cases: Add customers who completed a purchase to a "Buyers" segment, move high-engagement users into a VIP segment based on activity scores, or segment customers based on data from external systems.

Remove Customer from Segment removes one or more customers from a specified segment. This is the counterpart to Add Customer and is essential for maintaining accurate segment membership as customer status changes.

Key parameters:

• Credential to connect with: Required dropdown for authentication.
• Resource: Set to "Segment."
• Operation: Set to "Remove Customer."
• Segment ID: Required text field identifying the segment to modify.
• Customer IDs: Required text field listing which customers to remove from the segment.

Use cases: Remove churned customers from active user segments, update segment membership when subscription tiers change, or clean up segments based on inactivity thresholds.