Clients and links
What a client is, how their link and passkey work, and what each client status means.
A client is a business you build automations for. Each one gets a link that opens their own page. The first time, they save a passkey there, then connect what you asked for. There's no account to make, and from then on their page opens only with their passkey.
What you give each client
| Field | Used for | |
|---|---|---|
| Name | Required, up to 120 characters | Shown on their page and in alerts |
| Optional | Emailing them their link, and telling them about every change to what's connected | |
| Services | At least one | What their page asks them to connect. See Connections |
How many new clients you can add each month depends on your plan. See Plans and limits.
Client statuses
A client's status comes from the services you asked for:
| Status | What it means | What to do |
|---|---|---|
| Waiting | Nothing you asked for is connected yet | Send their link, or a reminder |
| Partly connected | Some services connected, not all | Ask them to open their link again and connect the rest |
| Ready | Everything you asked for is connected | Nothing. Workflows can run |
| Needs reconnecting | At least one service's access ended | Ask them to open their page and reconnect, or email them their link |
Needs reconnecting outranks the others. If even one service's access ended, the whole client shows Needs reconnecting, because that's what breaks workflows. Dashboard lists put these clients first.
In the API, the statuses are waiting, partial, ready and expired.
Ready, once
When a client connects everything you asked for, you get a notification, an email and a client.completed webhook. It happens once per client; asking for more services lets it happen again.
The link and their passkey
Links travel by email and chat, and inboxes get hacked. So a link on its own only ever opens the page. Everything else takes the client's passkey: Face ID, Touch ID, Windows Hello, a security key, or their phone.
| What happens | |
|---|---|
| First visit | Their page shows what you asked for and asks them to Save a passkey. Nothing can be connected before they do. They have 7 days from when the link was made to save it |
| After that | The link keeps working for as long as they're your client, and the page opens once their passkey confirms it's them. They can connect, reconnect, change and remove anything, and see every call your workflows make with their access |
There's no password, and nothing is ever emailed that opens their page, so someone reading their inbox gets nowhere. Whoever saves the first passkey on a link owns that page, which is why a link stops accepting a first passkey after 7 days.
- Did they open it? The client's page in the dashboard shows when they first opened it, and whether they've saved a passkey.
- Asking for more? Add the services under Details. They're emailed to open their page and connect them, with the same link.
- The link ran out before they saved a passkey? Email link: they get a new one.
- Shared with the wrong person before they saved a passkey? Press Make a new link. Anyone opening the old link is asked for a fresh one.
The account they connected with
When a client connects Google or Microsoft, we remember which account they used, such as jane@bakery.com, and show it on their client page. If they connect a different one later, you and the client are both emailed.
Check who connected
If an account on a client's page isn't one you expect, someone else may have opened their link before they did. Remove the client's connections, confirm with them by phone, and help them back in with a new passkey.
Lost passkeys
Passkeys usually sync through iCloud Keychain, Google Password Manager or a password manager, so a new phone already has theirs. They can also add a passkey on a second device from their page, so losing one doesn't lock them out.
If they do lose every passkey, they get back in through you:
- Confirm it's really them some other way, such as calling a number you already have.
- On the client's page in the dashboard, press Help them back in. Only owners can, and the client needs an email address on file, because we always email them that an invite was made. You get a link, which you can email, and a six-digit code to read out to them. The code is never emailed, so an invite in a hacked inbox is no use on its own. Invites work for 3 days.
- They open the link, enter the code, and save a new passkey. It replaces the ones they lost and signs out every browser.
Their connections keep working the whole time, so your automations don't stop.
Seeing their page
Press Preview beside their link. Signed in to the dashboard, you see what they'll see, but you can't save a passkey, so opening the link never takes the page from them. To try it with your own accounts, open the link in a private window.
Changing what you ask for
Edit the services under Details on the client. Their link asks for the new set at once.
| You… | What happens |
|---|---|
| Add a service | It shows Waiting and the client is no longer Ready. They're emailed to open their page and connect it. Same provider as one they have, like Gmail next to Sheets? They press Connect again to approve the extra permissions |
| Deselect a service | We stop asking for it. Access they already gave stays: use Disconnect to end it. See Removing access |
Removing a client
Remove client cancels every connection with its provider where possible, deletes them, and stops the link working. It can't be undone. See Removing access.