Connect a workspace to Zapier
Follow the approved Britixo Zapier connection flow, review consent and verify the selected workspace before creating live automations.
Before you begin
Confirm connector availability with your administrator. If support has supplied an app invitation or a specific setup link, use that approved link and check that it belongs to Zapier.
CRM workspace → Tools → Britixo Automations (or Utilities in a classic layout)
Follow these steps
- In Zapier, add the approved app to a new Zap or open its app connection. If the app is not listed, request the approved access route from Britixo support.
- Choose the app’s connection option and enter your confirmed workspace base URL when requested.
- Sign in to the correct CRM staff account on your own workspace. Complete any normal verification privately.
- Review the workspace, the signed-in account and the requested permissions on the consent page. Approve only if they match the intended workflow; otherwise choose Cancel.
- Return to Zapier, run the connection test and give the connection a clear company-specific name.
- Continue with one fictional lead test before publishing the Zap.
Check the result
Zapier accepts the connection test and shows the intended workspace and account. A separate workflow test then confirms the source and destination behaviour.
Rules, fields and operating limits
- The CRM overview itself has no Connect button.
- The normal consent flow uses the existing staff sign-in; it does not ask you to invent a new API password.
- Do not paste OAuth credentials into an ordinary Zap field or a support message.
If something does not look right
If consent returns an error or the app is unavailable, stop at that point and send support the visible message, time and public workspace address. Never send a code, access token or client secret.
Questions and answers
I cannot find Britixo in the Zapier app list. What now?
Ask support to confirm the approved app name, invitation or assisted setup. Do not choose an unrelated app with a similar name, and do not assume a public listing exists.
Why am I taken to a CRM sign-in page?
The workspace authenticates the staff member before allowing consent. Confirm the address and sign in using the normal authorised account.
Why does the consent page mention Britixo?
The connector uses shared Britixo technology and some consent wording retains that name. Confirm the workspace name, URL and account shown; cancel if any of them are wrong.
Can I decline the requested access?
Yes. Choose Cancel. No authorisation code is issued by that decision. If you already connected earlier, follow the separate disconnect process for that existing connection.
Does approval create a lead?
Approving consent creates connection authorisation, not a lead. A later Create Lead test or published action can create a real CRM record.
Can I leave the authorisation page open indefinitely?
Complete the flow promptly. Authorisation codes are short lived and single use. If the flow expires, restart from Zapier rather than reusing a code or old browser address.
Why does the connection need testing after approval?
Consent confirms permission. A connection test checks that Zapier can use the returned credentials for the correct workspace.
Should I use a browser extension or send my password to support?
Use only the normal approved browser connection flow. Support does not need your password, verification code, browser cookie or OAuth tokens.
Useful next steps
Contact Britixo support. Include the workspace, action, run reference and time; keep credentials private.