For the complete documentation index, see llms.txt. This page is also available as Markdown.

Customers

Every customer using your embedded integrations.

Customers · /settings/customers

A top-level item in the sidebar's OPERATE group, beside Activity rather than inside it. Note the mismatch between where it sits and where it lives: the sidebar puts it under OPERATE, but its route is under /settings/. Linking to /customers gets you a Page not found.

The Customers table with a single row: testing, identifier testing underneath, 1 connection, status Active, ending in View connections — with an All tiers filter and a 1 customer count above
The second line under each name is the identifier you will see again as endOrgId.

A customer is one of your customers — a container for their connections, credentials and workflow data.

The table

Column
Notes

Customer

Display name, with the identifier underneath.

Connections

How many systems they have authorised.

Status

Active, or Pending admin activation.

A count sits above the table, and Search customers narrows it. View connections on each row filters Connections to that customer.

Status

Active — set up and usable.

Pending admin activation — created, but an administrator has not activated it. Its integrations will not run until they do.

Creating a customer

Create customer adds one manually, which is what you want when onboarding an account before they first sign in.

The identifier is the stable one — use your own account ID rather than a display name. It is what you will see again as endOrgId in the embed token response, and as the final tenant segment of a connection ID.

Customers and tenants

The product uses both words. Tenant is the column header on all three Triggers tables, and it is the last segment of the connection ID format:

Treat them as the same thing: one isolated customer container, called a tenant wherever the plumbing shows through.

Where customers show up elsewhere

Surface
What it does

⌘K search, CUSTOMERS group

Jump straight to one.

A Customer column on every connection.

Widget builder preview

The tenant selector renders the widget as a customer.

The USER selector scopes the generated snippet.

Triggers tables

A Tenant column on webhooks, schedulers and app events.

Last updated

Was this helpful?