Ortto

Connect AI agents to Ortto. Agents merge or create people by email, record custom activities to drive journeys, look people up, and discover typed custom field ids for downstream steps.

5 actions available

A form submission or purchase arrives upstream

Agent reads field ids with Get Custom Fields to map the payload

Agent upserts the contact with Merge or Create Person

Agent records the event with Create Custom Activity

Agent confirms the person with Get Person by Email

Marketing channel gets a count of new people synced

A destructive filter-based read result routes for review before bulk action

What This Integration Enables

An agent can merge or create a person matched by email, addressing every field by Ortto's strongly-typed `type::name` id convention. Common values pass through convenience inputs, and custom fields pass through a raw fields object keyed by field id. Because the merge is queued asynchronously, the agent works from the returned per-person acknowledgement rather than assuming an instant finished record. Get People reads a page of contacts with a filter object, chosen field ids, sorting, and pagination, and Get Person by Email is a convenience lookup that returns the first match or null. For behavior, the agent records a custom activity against a person, referencing a registered activity id and identifying the person by email, which is how purchases and bookings drive journeys and reporting. Get Custom Fields lists the account's typed field ids so downstream steps address the right field every time. Ortto exposes no event triggers in this integration, so flows start from the systems feeding it: a form, a checkout, or a CRM. The agent is the bridge between the systems where contacts and events originate and the journeys Ortto runs on them.

Without FlowRunner

Contacts duplicated The same person is added again because no merge-by-email runs

Fields addressed by guess A sync writes to the wrong field because ids are not looked up

Activities untracked Purchases and bookings never reach Ortto to drive a journey

With FlowRunner

Contacts merged on email Merge or Create Person matches by email and merges instead of duplicating

Fields addressed by id Get Custom Fields supplies the typed ids so writes land correctly

Activities recorded Create Custom Activity logs the event that starts a post-sale journey

Use Case Scenarios

Form Submission Into a Journey

The agent pulls new submissions from [Typeform](/integrations/typeform) with Get Form Responses, then calls Merge or Create Person to upsert each respondent by email with their answers mapped to raw fields. Because the merge is by email, a respondent who submits twice merges into one record instead of two.

Record a Purchase Event

After a store returns recent purchases, the agent calls Create Custom Activity to record a purchase event against each customer, driving a post-sale journey. The purchase becomes an activity Ortto can react to, not a row in a separate report.

Sync a Booking

When a [Calendly](/integrations/calendly) On Invitee Created trigger fires, the agent calls Merge or Create Person to sync the booker's details and Create Custom Activity to log the booking for follow-up automation. The booking both updates the contact and starts the journey.

Human-in-Loop Highlight

Get People runs against a filter object, and a broad or wrong filter can return far more people than intended. When that read is the input to a downstream bulk action (a mass activity, a segment export, a re-engagement send), acting on an unexpectedly large result set is the risk. When the agent is about to feed a filter-based read into a bulk step, it treats the go-ahead as a [human-in-the-loop](/concepts/human-in-the-loop/) moment. It pauses, shows the filter used, the count returned, and a sample of the matched people, and routes the decision to a marketing owner through Slack or email. The owner confirms the set is right, and the agent proceeds. The owner holds, and nothing runs against the wrong audience. Routine single-person upserts and activity logs flow through untouched; the bulk action gets a human first.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via Slack

Human decides

Agent resumes with decision

Agent Capabilities

5 actions

People

Merge or Create Person Creates a new person or merges data into an existing one, matched by email. Fields are addressed by Ortto's typed `type::name` ids; common values pass through convenience inputs and custom fields through raw fields. The merge is queued asynchronously.
Get People Retrieves a page of people, specifying which field ids to return, an optional filter object, sorting, and pagination.
Get Person by Email Looks up a single person by email and returns the requested field ids. Returns the first match or null when none is found.

Activities and Fields

Create Custom Activity Records a custom activity event against a person, referencing a registered activity id and identifying the person by email. Creates the person if they do not yet exist. Custom activities power journeys and reporting.
Get Custom Fields Lists the custom person fields in the account, including each field's typed id, display name, and data type. Use these ids with Merge or Create Person, Get People, and Create Custom Activity.

Start building with Ortto

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us