Cloze

Connect AI agents to Cloze, a relationship-focused CRM that unifies contacts and every communication with them. Agents create people and companies, attach them to projects, and read the full timeline of messages behind a relationship.

32 actions API key available

Platform Documentation ↗

A scheduled sync run starts, or a form submission arrives from elsewhere

Get People Feed returns everything changed since the last cursor

Find People resolves which inbound records already exist by email address

Get Custom Fields confirms the field names an Additional Fields write will use

Create Person writes genuinely new contacts and logs their source

Add Communication Record puts the outreach on the relationship timeline

The relationship owner sees which of their contacts the sync wants to change

Owner approves the overwrites before the agent updates existing records

What This Integration Enables

Cloze's defining decision is that identity is resolved for you. People are matched by email address and companies by domain, and that matching runs on writes as well as reads. Create Person with an address Cloze already knows updates that record rather than creating a duplicate. That is a genuinely good product decision, and it changes what an integration has to think about. In most CRMs a create is safe and an update is risky. In Cloze there is no such thing as a safe create, because every create is a potential update to a relationship somebody else has been building.

FlowRunner agents work the whole model through this connector: people, companies, and projects, which is what Cloze calls deals, plus the timeline actions that put calls, meetings, notes, and content onto a relationship, message and email open data, and the webhook subscription lifecycle. Two mechanics do most of the useful work. Get People Feed returns a cursor you pass back on the next call, which makes incremental sync the default rather than an optimization. And Additional Fields lets an agent merge anything the connector does not surface directly, as long as the field names match the Cloze body exactly. Cloze ships no polling or realtime triggers here, because the delivered notification payload shape is not documented as a stable contract in the public reference, so webhook subscriptions are exposed as actions and change detection runs off the feed cursor. Agents move the data. The write that would overwrite a person's curated record is where human-in-the-loop orchestration earns its place.

Without FlowRunner

Timelines with holes in them Calls and meetings happen in other tools and never reach the relationship history

Full-table syncs every night The whole contact set gets pulled because nothing tracks what actually changed

Imports that quietly overwrite A bulk load lands on top of records a rep curated by hand, and nobody notices

With FlowRunner

One continuous timeline Every interaction from every tool arrives on the person it belongs to

Incremental sync by cursor Only records changed since the last run come back, so the sync stays cheap

Overwrites that get seen first Inbound values that would replace curated ones are shown before they are written

Use Case Scenarios

Incremental sync that stays cheap and stays current

On a schedule, the agent calls Get People Feed with the cursor from the previous run and receives only the contacts that changed. Each one is written into a warehouse table or a sheet in Google Sheets with its relationship stage, owner, and last interaction date. Because the cursor lives in the call rather than in a timestamp comparison, a run that fails halfway does not skip records on the next pass. The revenue team gets a contact table that reflects Cloze this morning instead of last Sunday's full export.

A relationship timeline that includes the work done elsewhere

A rep sends a sequence from an outreach tool and takes a call on a softphone. Neither of those lands in Cloze on its own. The agent calls Find People to resolve the contact, then Add Communication Record for the call and the emails, and Add Content Record for the deck that got shared. Create To Do puts the next step on the rep's list. When the deal has moved, Update Project shifts the stage using the project vocabulary of future, current, pending, won, and lost, which differs from the lead, future, current, past, and out set that people and companies use. The next person to open that contact sees one timeline, not three tool tabs.

Support and sales reading the same relationship

A ticket arrives from a known customer. The agent calls Find People on the sender's address, Get Person Timeline for the relationship history, and Get Messages with Get Message Body where the thread context matters. Retrieve Email Opens shows whether the customer ever opened the last two messages the account team sent, which is often the fastest explanation for a frustrated ticket. The summary posts into the support channel in Slack so the responder opens with context rather than with a discovery question. Because message bodies are personal communications, agents pull only the threads relevant to the ticket rather than sweeping the mailbox.

Human-in-Loop Highlight

In Cloze, Create Person is not a create. An email address that already exists resolves to the existing record and the supplied fields land on it. That makes a routine-looking bulk import the most dangerous operation in this connector, because a marketing list with stale job titles will happily overwrite the titles a rep confirmed on a call last week, and nothing about the call will look like a failure. So the import agent inverts the usual order. Before writing anything, it runs Find People or Get Multiple People across the inbound set to find which rows resolve to existing Cloze records, and compares the inbound values against what is already there. Genuinely new people go straight through Create Person. The collisions go to the relationship owner in Slack: "Importing 340 contacts from the conference list. 62 already exist in Cloze. 14 of those would change the job title, 9 would change the company, and 4 would change the relationship stage on records with activity in the last 30 days. Apply the inbound values, keep what is on the record, or apply only to the ones with no recent activity?" The agent then writes accordingly. Delete Person, Delete Company, and Delete Project are permanent and get the same treatment for the more obvious reason, but the overwrite is the one that would otherwise go unnoticed for months.

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

32 actions

People

Find People Searches people with filters and sorting, where the wire sort direction values are asc and dec. Used as the identity check before any write, since Cloze resolves people by email address.
Get Person Retrieves a single person. Used to load the full record before an update or an overwrite decision.
Get Multiple People Retrieves several people in one call. Used to check a whole inbound batch against existing records before an import writes anything.
Create Person Creates a person, or updates the existing record when the email address already exists in Cloze. Used for genuinely new contacts, and treated as an update path whenever the address may already be known.
Update Person Updates a person, matched by email address or by a portableId supplied through Additional Fields. Used to enrich records once the overwrite question has been settled.
Delete Person Permanently removes a person from the account. Cannot be undone, so it stays behind a human decision.
Get Person Timeline Returns the full relationship timeline for a person. Used to give a rep or a support responder real context before they reply.
Get People Feed Returns changed people along with a cursor to pass back on the next call, fetching only what changed since the previous run. This is the recommended way to keep an external system in step with Cloze.

Companies

Find Companies Searches companies with filters and sorting. Used to resolve an account before writing to it, since Cloze matches companies by domain.
Get Company Retrieves a single company. Used to load account context before a decision or a write.
Create Company Creates a company, or updates the existing record when the domain already exists. Used when a new account appears, with the same overwrite caution as people.
Update Company Updates a company matched by domain. Used to keep account detail current from an external source of truth.
Delete Company Permanently removes a company from the account. Cannot be undone.
Get Company Timeline Returns the account-level timeline. Used to see everything that has happened across the relationship rather than with one contact.

Projects

Find Projects Searches projects, which is what Cloze calls deals, with filters and sorting. Used for pipeline sweeps and stage reporting.
Get Project Retrieves a single project including its stage. Used to confirm state before a move.
Create Project Creates a project with a stage drawn from the project vocabulary of future, current, pending, won, and lost. Used to open a deal from an event elsewhere.
Update Project Moves a project through its stages or updates its detail. Used to keep the pipeline in step with what happened outside Cloze.
Delete Project Permanently removes a project. Cannot be undone.
Get Project Timeline Returns the timeline attached to a project. Used to review deal history before a forecast call.
Get Similar Projects Returns projects Cloze considers similar to a given one. Used to find comparable deals when sizing or qualifying a new opportunity.

Timeline

Create To Do Creates a to do on the timeline. Used to put a next step on a real list rather than in a rep's memory.
Add Communication Record Logs a call, meeting, text, or email to the relationship timeline. Used so work done in other tools still lands where the relationship is read.
Add Content Record Logs shared content to the timeline. Used to record what was actually sent alongside the conversation about it.

Messages

Get Messages Returns messages for a relationship. Used to reconstruct context for a support or sales handoff.
Get Message Body Returns the body of a specific message. Used sparingly, and only for the thread that a decision actually depends on.
Retrieve Email Opens Returns email open data. Used to tell the difference between a customer who disagreed and a customer who never saw the message.

Account

Get User Profile Returns the profile of the account the key belongs to, including the scopes granted to that key, which govern which resources it may read or change. Used to confirm access before a run commits to anything.
Get Custom Fields Returns the account's custom field definitions. Used before an Additional Fields write, because those field names must match the Cloze body exactly.

Webhooks

List Webhook Subscriptions Returns the registered webhook subscriptions. Used to audit what is already listening before adding more.
Subscribe To Webhook Registers a target URL for a change event such as person.change, company.change, or project.change, including their audit variants. Used to receive posts at an endpoint of your own, since no realtime trigger ships with this connector.
Unsubscribe From Webhook Removes a webhook subscription. Used deliberately, because another flow may be depending on the delivery.

Frequently Asked Questions

What can FlowRunner do with Cloze?

FlowRunner agents can run Find People, Get Person, and Get Multiple People in Cloze, plus 29 more actions.

Does connecting Cloze to FlowRunner require OAuth?

No. Cloze connects to FlowRunner with an API key, no OAuth flow required.

Can Cloze trigger a FlowRunner workflow automatically?

Cloze doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Cloze

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

Start Building Free Talk to us