Ortto (Autopilot) and Basin Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Keep Ortto (Autopilot) and Basin matched by integrating their events and actions. When marketing events happen in Ortto (Autopilot), update the Basin automatically - without any line of code in visual workflow builder.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about Ortto (Autopilot) and Basin

Detailed info you need to know about Ortto (Autopilot) and Basin integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Ortto (Autopilot)

    • Marketing
    • 4 triggers
    • 6 searches
    • 10 actions

    Manage contacts, accounts, audiences, and journeys in Ortto, formerly Autopilot.[5]

  • Basin

    • Marketing
    • 1 trigger
    • 13 searches
    • 18 actions

    Form backend that collects submissions, filters spam and forwards them to your tools.[6]

How to connect Ortto (Autopilot) to Basin

Set up your Ortto (Autopilot) and Basin integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Ortto (Autopilot) and Basin work in WEXTL?

WEXTL exposes actions and triggers for Ortto (Autopilot) and Basin that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

Ortto (Autopilot) triggersBasin actions

Ortto (Autopilot) modules

  • Archive Contacts Archives one or more contacts and reports how many were archived. A contact must be archived before it can be deleted.
  • Create a Custom Field Adds a custom field for people, with a Name and a Type of Text, Number or Date. The new Field ID is the output.
  • Create or Update a Contact Saves a contact matched on Email, creating it when it is new. Add Tags to label the contact and Fields for the rest of its data. Its Contact ID is returned afterwards.
  • Create or Update an Account Saves an account, creating it or updating the existing one. Add a Name and Domain, and use Fields for any other account data. Afterwards you receive the Account ID.
  • Delete Contacts Deletes contacts that are already archived and reports the count of removed contacts. Archive them first.
  • Get a Campaign Report Fetches the analytics report of one campaign, giving back its Campaign ID.
  • Get a Contact Finds one contact with its Email or Contact ID, returning only the requested Fields.
  • List Audiences Lists your marketing audiences by Audience ID and Name. Use Search term to find audiences by text, and Limit to read fewer.
  • List Campaigns Shows the campaigns and journeys running between a From date and a To date. Set Type to Journey or Campaign to see one kind.
  • List Contacts Pulls contacts that match a Filter, including only the requested Fields. Use Limit to read the first batch.
  • List Tags Returns the contact tags in your account, each with its Tag ID and Name. Use Limit to read only some.
  • Log an Activity Event Records custom activity events, up to 100 per call, that can trigger journeys. Send them as Activities, each with an Activity ID, an Email and Attributes.
  • Make an API Call Runs a free-form request against the Ortto (Autopilot) REST API using your saved credential.
  • Modify an Activity Definition Edits an activity definition identified by Activity ID, changing its Name or Attributes.
  • Subscribe or Unsubscribe a Contact to an Audience Changes audience membership for several People, each by Email with a Subscribed flag. Turn on SMS opted in to also record SMS consent.
  • Update a Custom Field Renames a custom field for people through Name, and gives the Field ID of the field that changed.
  • Watch Added Contacts Starts the workflow the moment a contact is added, with the Contact ID, Email and First name in the output. Ortto has no webhook subscription API, so paste the URL into a Webhook data source.
  • Watch Journey Entries Triggers instantly when a contact enters a journey. The Campaign ID and Email of the contact arrive with it.
  • Watch Journey Exits Triggers instantly as a contact leaves a journey, with the Campaign ID and First name of the contact.
  • Watch Updated Contacts Fires instantly when a contact changes and passes along the Contact ID, Last name and Email. The webhook URL is pasted into an Ortto Webhook data source.

Basin modules

  • Create a Form Sets up a Basin form from a Name. Use Redirect URL to send visitors elsewhere after a submission, Notification Emails to alert your team and Autoreply to answer the submitter.
  • Create a Form Webhook Makes Basin post every submission of a Form to a web address. Set Format to choose the payload type and turn on Run for Spam to include spam-marked entries.
  • Create a Mail Template Saves a reusable email template under a Project, from its Name and raw HTML Body.
  • Create a Project Adds a project that groups forms and mail templates.
  • Delete a Form Removes a form together with all of its submissions. This cannot be undone.
  • Delete a Form Webhook Removes a webhook so submissions stop being posted to its address.
  • Delete a Mail Template Removes a saved email template from Basin.
  • Delete a Project Deletes a project. Basin does not document what happens to the forms in it.
  • Delete a Submission Deletes a single form submission, and the action cannot be undone.
  • Get a Form Reads one form to get its UUID, Timezone, Project Name and Redirect URL.
  • Get a Form View Shows one recorded visit to a form, with the Form UUID it belongs to and its Created At time.
  • Get a Form Webhook Reads a webhook with its URL, Format, Enabled state and Trigger When Spam setting.
  • Get a Mail Template Returns a template by Mail Template ID, along with the Project ID it sits in and the Body markup.
  • Get a Project Looks up one project to read its Name and when it was created or last changed.
  • Get a Submission Finds one submission by Submission ID. Returns the sender Email and Payload Params, plus flags for Spam, Read and Trash.
  • List Domains Shows the domains registered to your Basin account. Use Query to match text, Page to move through results and Limit to cap the count.
  • List Form Views Returns recorded views of your forms. Use Query to filter by id, uuid, form id or form uuid and Limit to set how many to read.
  • List Form Webhooks Gathers the webhooks configured across your forms, one item each. Use Query to narrow the set.
  • List Forms Pulls your forms, each with its Name and Project Name. Filter them by id, name, uuid or project id through Query.
  • List Mail Templates Finds the email templates of one Project. Use Page to step through them and Limit to cap how many are read.
  • List Projects Fetches your projects, each with a Name and a Created At time. Use Query to find one by text.
  • List Submissions Browses form submissions. Use Form to limit it to one form, Status and Date From to narrow the range and Order By to sort them.
  • Make an API Call Calls the Basin REST API directly with a free-form request under your saved credential.
  • Re-fire Webhooks for a Submission Sends the webhooks of one submission out again, so receivers may see it a second time.
  • Re-fire Webhooks for Several Submissions Replays webhooks for a batch of Submission IDs in a single call. Receivers may see those submissions again.
  • Submit a Form Posts an entry to a Basin form as a visitor would, with one row of Fields per value. Set Client IP to record the visitor address.
  • Update a Form Edits an existing form, such as its Name, Redirect URL, Notification Emails or spam checks. Use Clear Fields to empty a value.
  • Update a Form Webhook Edits a webhook to change its URL, switch Enabled on or off, or move it to another Form. Changing the URL of a webhook created by Watch New Submissions stops that trigger.
  • Update a Mail Template Replaces the Name or Body of a mail template. Add the ETag (If-Match) of the version you read and Basin refuses the write if it changed since.
  • Update a Project Retitles an existing project with a new Name.
  • Update a Submission Flags a submission as spam or not with Spam, as read with Read, or moves it to the trash with Trash.
  • Watch New Submissions Starts the workflow the moment Basin receives a form submission, through an instant webhook. Each run gets the Submission ID, Email and Attachments.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with Ortto (Autopilot) and Basin integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Ortto (Autopilot) and Basin on WEXTL®

Claim your 3-day trial to build Ortto (Autopilot) with Basin integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Ortto (Autopilot) and Basin.

How do I connect Ortto (Autopilot) and Basin?

Connect your Ortto (Autopilot) and Basin 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]

What can I automate between Ortto (Autopilot) and Basin?

Example: when the "Watch Added Contacts" trigger in Ortto (Autopilot) fires, WEXTL can "Create a Form" in Basin. Ortto (Autopilot) has 4 triggers (including Watch Added Contacts, Watch Journey Entries, and Watch Journey Exits). Basin has 31 actions (including Create a Form, Create a Form Webhook, and Create a Mail Template). Add filters and transforms between steps when you need them.[1]

Can Ortto (Autopilot) trigger actions in Basin, and Basin in Ortto (Autopilot)?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate Ortto (Autopilot) and Basin?

No. Ortto (Autopilot)-to-Basin automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does Ortto (Autopilot) integrate with Basin in real time?

Yes. Trigger-based automations start the moment Ortto (Autopilot) (or Basin) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a Ortto (Autopilot) + Basin integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect Ortto (Autopilot) with Basin?

You can build your Ortto (Autopilot) + Basin automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Ortto (Autopilot) and Basin integration.

  1. Ortto (Autopilot) and Basin integration source code, module specs and credentials implementation.
  2. Our Ortto (Autopilot) and Basin integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Ortto (Autopilot) and Basin, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. Ortto (Autopilot) integration information
  6. Basin integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Ortto (Autopilot) and Basin integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Ortto (Autopilot) and Basin, or get started