STEP 1
Connect Autopilot and Omnisend
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 Omnisend Integration
Build marketing workflows between Autopilot and Omnisend on a visual canvas — set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Autopilot and Omnisend
Detailed info you need to know about Autopilot and Omnisend integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Autopilot to Omnisend
Set up your Autopilot and Omnisend integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Autopilot and Omnisend 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 Omnisend. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Autopilot and Omnisend work in WEXTL?
WEXTL exposes actions and triggers for Autopilot and Omnisend 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 triggersOmnisend 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.
Omnisend modules
- Add Tags to ContactsAdds the specified tags to contacts matched by ID, email, phone, or segment.
- Cancel CampaignCancels a scheduled or started campaign.
- Connect BrandConnects a site to Omnisend, registering its platform, version, and website with the brand.
- Copy AutomationCreates a disabled copy of an existing automation workflow.
- Copy CampaignCreates a new draft campaign as a copy of an existing one.
- Create AutomationCreates a new automation workflow as a disabled draft.
- Create BatchCreates a batch job that asynchronously creates or updates up to 100 items of one resource type.
- Create CampaignCreates a new campaign draft.
- Create Custom Event MetadataDeclares a new brand-custom event schema identified by its name and origin.
- Create Email TemplateCreates a new email template.
- Create or Update ContactCreates a new contact, or updates the matching contact when the email identifier already exists.
- Create ProductCreates a new product in the product catalog.
- Create Product CategoryCreates a new product category.
- Create SegmentCreates a new segment defined by condition-based rules.
- Create Universal LayoutCreates a new universal layout.
- Delete AutomationPermanently deletes an automation workflow.
- Delete CampaignPermanently deletes a campaign.
- Delete Email TemplatePermanently deletes an email template.
- Delete ImagePermanently deletes an image by its unique ID.
- Delete ProductDeletes a product from the product catalog.
- Delete Product CategoryRemoves a product category.
- Delete SegmentDeletes a segment by its ID.
- Delete Universal LayoutPermanently deletes a universal layout.
- Disable AutomationDisables an automation workflow so it stops accepting new trigger events.
- Enable AutomationEnables an automation workflow so it starts processing trigger events.
- Generate Analytics ReportRuns a send-date analytics report across delivery, engagement, and revenue metrics; limited to 55 requests per 24 hours per brand.
- Generate Analytics StatisticsRuns an event-date analytics report across engagement and audience-growth metrics; limited to 55 requests per 24 hours per brand.
- Get AutomationRetrieves a single automation workflow by ID.
- Get Automation UTMRetrieves the aggregated UTM tags for every send-action block in an automation.
- Get BatchRetrieves the status and progress of a single batch job by its ID.
- Get Batch ItemsRetrieves a batch's full result envelope, with per-item outcomes for successes and failures.
- Get Block UTMRetrieves the UTM tags for a single automation send-action block.
- Get CampaignRetrieves a single campaign by ID.
- Get Campaign UTMRetrieves UTM tag settings for a campaign.
- Get ContactRetrieves a single contact by its unique ID.
- Get Current BrandRetrieves details about the currently connected brand.
- Get Email ContentRetrieves an existing email content by ID.
- Get Email TemplateRetrieves an existing email template by ID.
- Get ImageRetrieves a single image by its unique ID.
- Get ProductRetrieves a single product by its ID.
- Get Product CategoryRetrieves a single product category by its ID.
- Get SegmentRetrieves a single segment by its ID.
- Get Segment StatisticsRetrieves contact-count statistics for a segment.
- Get Universal LayoutRetrieves an existing universal layout by ID.
- Import Email Template from HTMLImports a new email template from raw HTML source.
- List AutomationsRetrieves a paginated list of automation workflows.
- List BatchesRetrieves a paginated list of batch jobs filtered by endpoint, status, and date range.
- List CampaignsRetrieves a paginated list of campaigns.
- List ContactsRetrieves a paginated list of contacts filtered by the provided criteria.
- List Email TemplatesRetrieves a paginated list of email templates.
Frequently asked questions
Common questions about connecting Autopilot and Omnisend.
Connect your Autopilot and Omnisend 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 Tags to Contacts" in Omnisend. Autopilot has 4 triggers (including Watch Contact Added, Watch Contact Updated, and Watch Journey Entered); Omnisend has 83 actions (including Add Tags to Contacts, Cancel Campaign, and Connect Brand). 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-Omnisend 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 Omnisend) 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 + Omnisend 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 Omnisend integration.
- Autopilot and Omnisend integration source code, module specs and credentials implementation.
- Our Autopilot and Omnisend integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Autopilot and Omnisend — 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
- Omnisend integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library