Autopilot by Ortto Make integrationAutomate Autopilot by Ortto with Make.

You get a contact enrolled in one of your Ortto journeys straight from Make, so the emails of that sequence start without anyone clicking in Ortto. It is the step that turns a new lead into an active campaign.

Places an existing contact on one of your lists, which is a clean way to group people by source or interest. Other modules can then read, check or clean that list from Make.

Creates a brand new list in Ortto from your scenario, so a new event, product or campaign gets its own audience without manual setup. The list is then available to the other list modules.

Answers a simple question for one person: is this contact on that list or not? The result lets the rest of the scenario take a different road depending on the answer, instead of adding duplicates blindly.

Writes a person into your Ortto database, and if the contact already exists, the module updates it. That makes it the safest entry point for leads coming from forms, shops or events.

Removes a contact from your Ortto database entirely, which keeps your audience clean when someone asks to be forgotten. It targets one contact per run, identified by the ID you map.

Clears the activity history of a contact while leaving the contact record itself in place. You keep the person in your lists but wipe the trail of what they did.

Fetches the full record of one contact, and you can look them up by contact ID or by email address. The details then feed the next modules, for instance to enrich a CRM entry or personalize a message.

Retrieves the data of an email campaign, starting from an ID that appears in the Autopilot Activity Stream. Handy when you want to report on a campaign outside Ortto or store its details elsewhere.

Reaches any endpoint of the Ortto API that the other modules do not cover, with the same connection you already created. It is the escape hatch when a ready-made module is missing.

Takes a contact off a list without deleting them from Ortto, so they leave that audience while staying in your database. It is the gentle alternative to a full deletion.

Stops a contact from receiving the emails sent by your Autopilot journeys, while the record stays in your database. It respects an opt-out that was captured somewhere other than Ortto.

Changes the details of a contact who already exists and sends back that contact's ID number. That returned ID is useful to chain a list or journey module right after the update.

Returns your Ortto contacts as a series of bundles, one per person, ready to be copied or checked elsewhere. As a search, it can return zero, one or many results.

Gives you every list available in your Ortto account, which helps when you need list IDs or want an overview of what exists. Each list comes out as its own bundle.

Reads all the contacts sitting on one list and hands them over one by one to the rest of the scenario. You get exactly the audience of that list, not the whole database.

Pulls the people who currently match one of your smart segments, so a segment built in Ortto can drive actions in other tools. Each matching contact becomes a bundle.

Shows the API triggers of your account together with the journey name each belongs to, so you can tell journeys apart before sending anyone into one. It removes the guesswork from journey IDs.

Returns every smart segment defined in your Ortto account, one bundle each, so you can see what audiences you already have before building on them. It pairs naturally with the segment contacts search.