Where to start
CRM workspace → Tools → Britixo Automations (or Utilities in a classic layout)
Before you begin
Decide whether the Zap needs to read leads, create leads or receive new-lead events. Review those needs with the workspace administrator before approving access.
Follow these steps
- Check the staff account is active in the intended workspace.
- Match requested capabilities to the workflow: identity, read leads, create leads and/or manage event subscriptions.
- Ask the administrator to review Global View and Create permissions for Leads as needed.
- Read the consent page before approving. Cancel and seek clarification if a capability is unexpected.
- Retest affected Zaps after staff permissions, account status or connection ownership changes.
Check the result
The authorising account has sufficient permission for the intended actions and the team understands that later access changes can stop those actions.
If something does not look right
For an unauthorised or insufficient-permission error, check the account and requested operation first. Reconnecting does not grant a permission that the staff account does not have.
Fields, rules and limits
- identity.read confirms the connected account and workspace.
- leads.read needs Global View for Leads; leads.write needs Create for Leads.
- webhooks.manage needs Global View for Leads. Current staff access is rechecked during API use and event delivery.
Questions and answers
Can a connection read leads after View access is removed?
The connector rechecks the relevant permission. Removing it can prevent further reading or event delivery; plan and test access changes.
Does Create permission also allow reading every lead?
No. Lead reading and lead creation are separate capabilities. A Zap that both searches and creates needs both corresponding permissions and scopes.
Is View own enough for a new-lead trigger?
Not for this connector. Webhook management requires Global View for Leads, so an administrator must review whether that level of access is appropriate.
Can Zapier change my staff role?
The current connector exposes identity and lead operations, not staff-role management.
Can another company use my token?
The connection is checked in the workspace where it was issued. Connect each company separately and keep all credentials private.
What if a staff member leaves?
Pause the affected Zaps, arrange an approved replacement connection and have the former connection revoked. Do not keep a departed person’s account active simply to preserve an automation.
Useful next steps
Contact the Proplix team if you need help with your setup. Include the page or record reference and a description of the issue; leave passwords and private access tokens out of the message.