STEP 1
Select Autopilot in workflow
Pick Autopilot app in the workflow builder [4] - just one click to select the app.
Autopilot Integration
Manage contacts, accounts, audiences, and journeys in Ortto (formerly Autopilot). Turn Autopilot engagement into automated marketing workflows that keep leads and audiences moving. Start with Watch Contact Added, then use Get Campaign Report and Get Contact to trigger the next step.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Supported triggers and actions for Autopilot integration
Triggers can detect changes in Autopilot and run actions that can create, search or modify data inside Autopilot automatically [3] — exactly how you set them.
- Watch Contact AddedWatch Contact Added — Ortto has no API to subscribe a webhook, so this connects manually. In Ortto, go to Data sources → New data source → Webhook (advanced), paste the URL shown above, then attach this webhook as a data destination on the built-in Person created CDP activity.
- Watch Contact UpdatedWatch Contact Updated — Ortto has no API to subscribe a webhook, so this connects manually. In Ortto, go to Data sources → New data source → Webhook (advanced), paste the URL shown above, then attach this webhook to a tracked field-change activity.
- Watch Journey EnteredWatch Journey Entered — Ortto has no API to subscribe a webhook, so this connects manually. In Ortto, go to Data sources → New data source → Webhook (advanced), paste the URL shown above, then add a Send to Webhook action at the start of your journey and select this webhook.
- Watch Journey ExitedWatch Journey Exited — Ortto has no API to subscribe a webhook, so this connects manually. In Ortto, go to Data sources → New data source → Webhook (advanced), paste the URL shown above, then add a Send to Webhook action at the end of your journey and select this webhook.
- Get Campaign ReportReturns analytics for a campaign.
- Get ContactReturns a single contact by email or ID.
- List AudiencesRetrieves marketing audiences.
- List CampaignsRetrieves campaigns and journeys in a date range.
- List ContactsRetrieves a list of contacts.
- List TagsRetrieves contact tags.
- Archive ContactArchives one or more contacts.
- Create Custom FieldCreates a person custom field.
- Create or Update AccountCreates or updates an account.
- Create or Update ContactCreates or updates a contact by email.
- Delete ContactPermanently deletes archived contacts.
- Log Activity EventLogs custom activity events that can trigger journeys.
- Make an API CallPerforms an arbitrary authorized API call.
- Modify Activity DefinitionModifies an activity definition.
- Subscribe or Unsubscribe Contact to AudienceSubscribes or unsubscribes contacts from an audience.
- Update Custom FieldUpdates a person custom field.
How to integrate Autopilot in automation workflow?
3 simple steps to make your Autopilot connected with other apps in automation workflows on WEXTL. Up to 10 minutes integration set up.
STEP 2
Connect Autopilot
When prompted, authorize access to Autopilot in WEXTL once. Autopilot credentials are encrypted and never shared with WEXTL. Authorization will be reused in any future API calls [3].
WEXTL wants to integrate with your Autopilot account. Approve?
STEP 3
Build a workflow
Build your workflow with Autopilot yourself or with WEXTL® AI Builder. Connect Autopilot to any available integrations [5], or use HTTP node to go beyond them.
Autopilot
How Autopilot connects and integrates with WEXTL
Save and approve your credentials once — WEXTL® stores authorization information encrypted and reuses the authentication whenever Autopilot app is called in workflows. That allows your marketing automations to run without your attention, per defined schedule [7]. Explore documentation [6] for a detailed list of fields that Autopilot supports.
The following table illustrates what fields Autopilot integration require during authorization flow inside our workflow builder [4].
Connect Autopilot
API Key*Text
••••••••
Region*Text
••••••••
Demonstration of Autopilot connection step inside WEXTL Workflow Builder [4].
| Field | Type | Help |
|---|---|---|
API KeyRequired | password | Ortto Settings → Integrations → API keys. |
RegionRequired | select | — |
Connect Autopilot to popular apps on WEXTL
Enter a name of the other app you want to sync with Autopilot below. Click on selected app to explore integration options with Autopilot. If the app you search for is not available in WEXTL yet, you can use HTTP node [10] instead to integrate it directly.
Example automation with Autopilot integration
Select Watch Contact Added trigger from Autopilot - this will be a starting point in your automation. Whenever event happens in Autopilot, workflow will start [7] from Watch Contact Added node.
Search for Create or Update Contact, connect it as the next step of integration sequence. You can use filters between Watch Contact Added and Create or Update Contact, so only important data pass from Watch Contact Added to the next step. WEXTL gives you full control over the process of Autopilot automation. All parts of workflow are visible on the canvas [4].
Autopilot on WEXTL has 20 modules for combining marketing automations. Explore Autopilot documentation for more.
Autopilot
Watch Contact Added
Bloomreach
Performs action
OR
Bloomreach
Triggers
Autopilot
Create or Update Contact
Demonstration of how visual Autopilot automation [6] looks in WEXTL.
Frequently asked questions
Common questions about automating Autopilot in your workflows.
Autopilot has 4 triggers, including "Watch Contact Added", "Watch Contact Updated", and "Watch Journey Entered", and more. Triggers are start points of the workflow, and automations may start from them.
Integration has 16 actions, including "Get Campaign Report", "Get Contact", and "List Audiences", and more. Refer to our Autopilot Documentation for detailed inputs and outputs.
No. Most automations are built visually on the canvas by picking triggers, actions, and mapping fields. You can add custom JavaScript with Functions when advanced logic is needed — but our customers do that in rare cases [4].
Yes. Connections are authenticated per account, credentials are encrypted at rest, and you can enforce approvals and team-level access controls on any automation.
The Autopilot integration on WEXTL runs directly on its vendor public API — every field name, authentication method, and rate limit is controlled by Autopilot official API and covered in documentation [3]. WEXTL handles the request signing and pagination for you.
Absolutely. Where Autopilot provides native webhooks, you can use instant triggers to eliminate polling delay. For custom webhooks, WEXTL offers Custom Webhook node, so you can start automation whenever Autopilot or any other service sends event to webhook URL.
WEXTL is an AI-first visual canvas. The platform allows you to describe automation in plain text — and AI will wire nodes for Autopilot inside the workflow builder [4]. You can also use built-in workflow nodes (AI Agent, Human in the Loop, Condition, Aggregate Results) in pair with Autopilot modules to craft complex integration flows with branches, filtering, and conditional logic. There are absolutely no limits of what you can build.
References
List of sources used to gather information about the Autopilot integration.
- Autopilot integration source code, module specs and credentials implementation.
- Internal Autopilot integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official Autopilot vendor API documentation — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® Visual Workflow Builder, anonymized data from our technical support team.
- WEXTL® Apps Library
- WEXTL® Autopilot App Documentation
- WEXTL® Workflow Scheduler
- WEXTL® HTTP node documentation