STEP 1
Connect Autopilot and Emarsys
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
Autopilot and Emarsys Integration
Keep Autopilot and Emarsys in sync by integrating their events and actions. When marketing events happen in Autopilot, update the Emarsys automatically - without any line of code in visual workflow builder.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Autopilot and Emarsys
Detailed info you need to know about Autopilot and Emarsys integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Autopilot to Emarsys
Set up your Autopilot and Emarsys integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Autopilot and Emarsys nodes onto the canvas [4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between Autopilot and Emarsys. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Autopilot and Emarsys work in WEXTL?
WEXTL exposes actions and triggers for Autopilot and Emarsys that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.
Autopilot triggersEmarsys actions
Autopilot modules
- 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.
- 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.
- 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.
- 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.
Emarsys modules
- Add Contacts to a Contacts ListAdds new contacts to an existing contact list.
- Create a Changed Contacts ExportCreates a new changed contacts export and returns its ID.
- Create a Contact ListCreates or updates a contact list with the provided parameters.
- Create a Contact List ExportCreates a new contact list export job and returns its ID.
- Create a Registered Contacts ExportCreates a new registered contacts export task and returns its ID.
- Create ContactsCreates new contacts in the system.
- Create or Update ContactsUpdates one or multiple contacts in the system.
- Delete a Contact ListDeletes a single contact list.
- Delete ContactsDeletes one or multiple contacts from an account.
- Download Export DataReturns a CSV file once the export job is finished. The distribution method must be set to Local when initiating an export job.
- Get a ContactReturns the field values of the contacts specified by either their internal identifiers or by a custom property.
- Get Export StatusRetrieves the status of a requested export.
- List Contact ListsRetrieves a list of existing contact lists.
- List ContactsReturns contacts from a specified contact list.
- Make an API CallPerforms an arbitrary authorized API call.
- Remove Contacts from a ListRemoves specified contacts from a provided list.
- Search ContactsSearches for contacts by specified criteria.
- Watch External EventsTriggers when an external event for a contact is initiated in a campaign or automation center program.
Frequently asked questions
Common questions about connecting Autopilot and Emarsys.
Connect your Autopilot and Emarsys accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them. [3]
Example: when Autopilot's "Watch Contact Added" fires, WEXTL can "Add Contacts to a Contacts List" in Emarsys. Autopilot has 4 triggers (including Watch Contact Added, Watch Contact Updated, and Watch Journey Entered); Emarsys has 18 actions (including Add Contacts to a Contacts List, Create a Changed Contacts Export, and Create a Contact List). Add filters and transforms between steps when you need them. [1]
Yes — the integration works in both directions. Use each app's triggers to start a workflow and the other app's actions to update it. [2]
No. Autopilot-to-Emarsys automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic. [4]
Yes. Trigger-based automations start the moment Autopilot (or Emarsys) fires a new event — webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control. [7]
A first automation typically takes 5–10 minutes: connect each app's credential once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.
You can build your Autopilot + Emarsys automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]
References
List of sources used to gather information about the Autopilot and Emarsys integration.
- Autopilot and Emarsys integration source code, module specs and credentials implementation.
- Our Autopilot and Emarsys integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Autopilot and Emarsys — 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.
- Autopilot integration information
- Emarsys integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library