ITERABLE n8n INTEGRATION: AUTOMATE ITERABLE WITH N8N

The Create or Update User action is the cornerstone of your Iterable integration, enabling you to maintain accurate and up-to-date user profiles automatically. This action intelligently handles both new user creation and existing user updates based on the identifier you provide—perfect for keeping your marketing database synchronized with your application.

Key parameters:

• Credential to connect with: Dropdown to select your Iterable API credentials. This is required for authentication.
• Resource: Set to "User" to target user-related operations. Required field.
• Operation: Set to "Create or Update" to enable upsert functionality—creating new users or updating existing ones seamlessly.
• Identifier: Dropdown to choose how users are identified (email or userId). Supports both fixed values and dynamic expressions for flexibility.
• Value: Text field where you enter the actual identifier value (the email address or user ID). Required to locate or create the correct user record.
• Additional Fields: Optional section to add custom user properties like name, phone number, subscription preferences, or any custom data fields your Iterable setup uses.

Use cases:

• Automatically create Iterable users when new accounts are registered in your application
• Sync profile updates from your CRM (HubSpot, Salesforce) to Iterable in real-time
• Enrich user profiles with data from third-party enrichment services
• Update user preferences when they modify settings in your app

The Get User action retrieves complete user profile information from Iterable, making it invaluable for building conditional workflows or syncing data to other platforms. Use it to check user status, retrieve custom fields, or verify that records exist before performing other operations.

Key parameters:

• Credential to connect with: Dropdown to select your Iterable account credentials. Required for API authentication.
• Resource: Set to "User" to indicate you're working with user data.
• Operation: Set to "Get" to fetch user information rather than modify it.
• By: Dropdown to specify the lookup method—currently supports "Email" to identify users by their email address.
• Email: Text input field for the specific email address of the user to retrieve. Required when using email-based lookup.

Use cases:

• Verify a user exists in Iterable before sending them to a specific campaign
• Retrieve user properties to personalize messages in other platforms
• Check subscription status before adding users to new lists
• Build conditional logic based on user attributes stored in Iterable

The Delete User action permanently removes a user record from Iterable, helping you maintain GDPR compliance and keep your database clean. When a customer requests data deletion or an account is terminated, this action ensures complete removal from your marketing system.

Key parameters:

• Credential to connect with: Dropdown to select your Iterable credentials for authentication. Required.
• Resource: Set to "User" since this action targets user records.
• Operation: Set to "Delete" to permanently remove the user.
• By: Dropdown to choose the identification method, set to "Email" for email-based user lookup.
• Email: Text input field where you enter the email address of the user to delete. Supports both fixed values and dynamic expressions. Required to identify the correct record.

Use cases:

• Automatically process GDPR deletion requests from your support system
• Remove users when accounts are deleted from your application
• Clean up test accounts after QA processes
• Handle unsubscribe requests that require complete data removal

The Add User to User List action enables precise audience segmentation by programmatically adding users to specific lists in Iterable. This is essential for building targeted campaigns, managing subscription preferences, and organizing your audience based on behavior or attributes.

Key parameters:

• Credential to connect with: Dropdown for selecting Iterable API credentials. Required.
• Resource: Set to "User List" to target list management operations.
• Operation: Set to "Add" to subscribe users to the specified list.
• List Name or ID: Text field to specify which list receives the user. Can be set as a fixed value or dynamic expression. Note: If the dropdown shows an error fetching options, enter the list name or ID manually.
• Identifier: Dropdown to choose how the user is identified (email, userId, etc.). Select the appropriate option for your workflow.
• Value: Text field for the actual identifier value of the user being added. Required.

Use cases:

• Add new customers to your onboarding email sequence automatically
• Segment users into interest-based lists based on their activity
• Move users to VIP lists when they reach spending thresholds
• Subscribe users to content categories they've expressed interest in

The Remove User from User List action handles the opposite operation—unsubscribing users from specific lists while keeping their overall Iterable profile intact. This is crucial for honoring opt-out preferences and managing list hygiene without deleting user data entirely.

Key parameters:

• Credential to connect with: Dropdown to select your Iterable credentials. Required for authentication.
• Resource: Set to "User List" for list-related operations.
• Operation: Set to "Remove" to unsubscribe users from the specified list.
• List Name or ID: Text field to identify which list to modify. If the dropdown shows connection issues, input the list name or ID manually.
• Identifier: Dropdown specifying how to identify the user (email, userId, etc.).
• Value: Text field for the user's identifier value. Required to target the correct user.
• Additional Fields: Optional parameters to customize the removal behavior.

Use cases:

• Automatically remove users from promotional lists when they convert to paid
• Process unsubscribe requests for specific content categories
• Remove inactive users from active campaign lists after a defined period
• Clean up list memberships when users downgrade their subscription tier

The Track Event action sends custom event data to Iterable, powering behavioral triggers, journey analytics, and personalized campaign logic. Every important user action in your application—purchases, feature usage, content consumption—can be tracked to drive smarter marketing automation.

Key parameters:

• Credential to connect with: Dropdown for selecting Iterable API credentials. Required.
• Resource: Set to "Event" to work with event tracking.
• Operation: Set to "Track" to send event data to Iterable.
• Name: Text input field for the event name you want to track (e.g., "purchase_completed", "feature_activated"). Essential for identifying the event type in Iterable.
• Additional Fields: Optional section to include event metadata like purchase amount, product category, feature name, or any custom properties relevant to your event.

Use cases:

• Track purchase events to trigger post-purchase email sequences
• Log feature activation events to measure product adoption
• Send content engagement events to personalize recommendations
• Record milestone achievements to trigger celebration campaigns