Skip to main content

Connection flow

After your backend has obtained a connect token (typically by exchanging an access token during token exchange), you open the Connect UI so the user can authorize an app. The Connect UI URL includes the app as a path segment and the connect token as a token query parameter. Optionally, pass a theme parameter to apply partner-specific branding to the Connect UI. There are two approaches.

Option 1: Popup with postMessage

Open the Connect UI URL in a popup window and listen for a message back with the connection ID.

Option 2: Redirect

Navigate the current window to the Connect UI URL with a redirect_uri. After the user authorizes, Zapier redirects back to your URL with the result as query parameters.
When Zapier redirects back, your callback URL receives:

On success

On error

Use authentication_id as the connection identifier with your access token.

Reconnecting

To reconnect an existing connection (e.g. after it expires), add the reconnect_id parameter to the Connect UI URL. This tells Zapier to re-authorize the same connection instead of creating a new one. The value is the connection’s ID.
Everything else — popup vs redirect, theme, postMessage handling — works exactly the same as a new connection.

Handling popup close

The user may close the popup before completing the flow. Since no postMessage is sent in that case, poll the popup’s closed property to detect this and reset your UI.