AUTOPILOT n8n INTEGRATION: AUTOMATE AUTOPILOT WITH N8N

This trigger fires the moment a new contact is created in your Autopilot account, making it the foundation for any lead capture or onboarding automation. Whether contacts come from form submissions, manual imports, or API calls, this trigger catches them all and launches your workflow instantly.

Configuration: The trigger includes two required parameters: Credential to connect with (select your Autopilot account credentials from the dropdown menu for authentication) and Event (set to "Contact Added" to activate on new contact creation).

Typical use cases: Instantly notify your sales team on Slack when a new lead enters your Autopilot database • Auto-enrich new contacts with third-party data providers like Clearbit or Hunter • Create corresponding records in your CRM (HubSpot, Salesforce, Pipedrive) • Add new contacts to a Google Sheet for reporting and tracking.

When to use it: This is your go-to trigger for any workflow that needs to react to new leads or contacts entering your marketing ecosystem. Perfect for lead scoring, instant follow-ups, and cross-platform synchronization.

This trigger activates whenever an existing contact's information changes in Autopilot—field updates, custom property modifications, or any data alteration. It's essential for keeping your contact data synchronized across multiple platforms.

Configuration: Select your authenticated Autopilot account from the dropdown (Credential to connect with - required). Choose "Contact Updated" from the available events (Event - required, can also accept expressions for dynamic configuration).

Typical use cases: Sync contact updates to your CRM like Salesforce in real-time, ensuring data consistency • Trigger re-engagement workflows when a contact's lifecycle stage changes • Update customer records in your billing system when contact details change • Log all contact modifications to a database for audit purposes.

When to use it: Implement this trigger when data synchronization is critical to your operations. It's particularly valuable for teams using multiple tools that need to maintain a single source of truth for contact information.

This trigger fires when a contact is added to a specific list in Autopilot, enabling you to build list-specific automation workflows. It's perfect for triggering targeted actions based on list membership.

Configuration: Choose your Autopilot credentials from the dropdown menu (Credential to connect with - required for API authentication). Select "Contact Added To List" to monitor list additions (Event - required parameter that determines which event type initiates your workflow).

Typical use cases: Send a welcome email sequence through another email provider when contacts join a specific list • Notify account managers when high-value prospects are added to a VIP list • Automatically tag contacts in your CRM like Attio based on their list membership • Trigger product-specific onboarding flows based on interest lists.

When to use it: Use this trigger when you need list-specific automation logic. It's ideal for segmented marketing campaigns, interest-based workflows, and membership-driven actions.

This trigger activates when a contact is removed from a list, allowing you to respond to list membership changes in real-time. Essential for maintaining clean data across your integrated tools.

Configuration: Select the Autopilot credentials needed for authentication (Credential to connect with - required dropdown parameter). Set to "Contact Removed From List" to monitor removals (Event - required fixed value selection).

Typical use cases: Remove contacts from corresponding segments in other marketing tools • Update your CRM to reflect changed list membership status • Trigger re-engagement campaigns for contacts removed from active lists • Log removal events for compliance and auditing purposes.

When to use it: Deploy this trigger when you need to maintain list parity across systems or when list removal should trigger specific business logic, such as downgrade flows or win-back campaigns.

This trigger fires when a contact unsubscribes from your communications, enabling immediate response to opt-out events. Critical for compliance and maintaining clean lists across all your marketing tools.

Configuration: Select credentials for your Autopilot account authentication (Credential to connect with - required parameter). The Event is fixed to "Contact Unsubscribed"—the trigger specifically responds to this single event type when a contact opts out of communications.

Typical use cases: Immediately update subscription status in all connected marketing platforms • Log unsubscribe events in your data warehouse for analysis • Trigger feedback request workflows to understand why contacts opted out • Update CRM records to prevent sales from reaching out to unsubscribed contacts.

When to use it: This trigger is non-negotiable for compliance. Deploy it to ensure unsubscribe preferences are respected across your entire tech stack instantly.

This trigger fires when a contact enters a dynamic segment in Autopilot, enabling behavior-based automation. Segments in Autopilot are dynamic—contacts enter and exit based on criteria—making this trigger perfect for behavioral workflows.

Configuration: Select your stored Autopilot credentials from the dropdown (Credential to connect with - required for authentication). Choose "Contact Entered Segment" from the available events (Event - required parameter, can be set as a fixed value or configured using expressions for advanced use cases).

Typical use cases: Alert sales when a contact enters a "High Intent" or "Ready to Buy" segment • Trigger personalized email sequences based on behavioral segmentation • Update lead scores in your CRM when contacts enter engagement-based segments • Create tasks for customer success when accounts enter at-risk segments.

When to use it: This is your behavior-driven trigger. Use it when contact actions and characteristics—not just list membership—should drive your automation logic.

This trigger activates when a contact exits a segment, allowing you to respond to behavioral changes or disqualification events. It complements the "Contact Entered Segment" trigger for complete segment lifecycle management.

Configuration: Select your Autopilot account credentials (Credential to connect with - required dropdown). Set to "Contact Left Segment" to monitor segment exits (Event - required parameter that accepts fixed text or expression input).

Typical use cases: Pause or stop active campaigns when contacts no longer meet segment criteria • Notify team members when contacts fall out of qualification segments • Update CRM stages when contacts exit specific behavioral segments • Trigger win-back campaigns when contacts leave engagement segments.

When to use it: Use this trigger to maintain accurate targeting and prevent irrelevant outreach. It's crucial for any workflow where segment membership drives ongoing actions.