STEP 1
Connect Autopilot and Gumlet
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 Gumlet Integration
Build marketing workflows between Autopilot and Gumlet 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 Gumlet
Detailed info you need to know about Autopilot and Gumlet integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Autopilot to Gumlet
Set up your Autopilot and Gumlet integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Autopilot and Gumlet 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 Gumlet. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Autopilot and Gumlet work in WEXTL?
WEXTL exposes actions and triggers for Autopilot and Gumlet 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 triggersGumlet 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.
Gumlet modules
- Add Asset to a PlaylistAdds an existing asset to a playlist.
- Complete a Multipart UploadCompletes a multipart upload after all files are uploaded to an S3 bucket via a generated presigned URL.
- Create a CollectionCreates a new video collection.
- Create a PlaylistCreates a new playlist.
- Delete a CollectionDeletes a single collection.
- Get a CollectionRetrieves a single collection.
- Get a Presigned URL for a Single Part UploadReturns a presigned URL for uploading a single-part video.
- List CollectionsRetrieves a list of video collections.
- Make an API CallPerforms an arbitrary authorized API call.
- Remove an Asset from a PlaylistRemoves an asset from a playlist.
- Search Video AssetsSearches for video assets.
- Update a CollectionUpdates an existing collection.
- Update a PlaylistUpdates an existing playlist.
- Watch EventsTriggers when a specific event occurs.
Frequently asked questions
Common questions about connecting Autopilot and Gumlet.
Connect your Autopilot and Gumlet 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 Asset to a Playlist" in Gumlet. Autopilot has 4 triggers (including Watch Contact Added, Watch Contact Updated, and Watch Journey Entered); Gumlet has 13 actions (including Add Asset to a Playlist, Complete a Multipart Upload, and Create a Collection). 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-Gumlet 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 Gumlet) 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 + Gumlet 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 Gumlet integration.
- Autopilot and Gumlet integration source code, module specs and credentials implementation.
- Our Autopilot and Gumlet integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Autopilot and Gumlet — 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
- Gumlet integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library