Where to start
CRM workspace → Tools → Britixo Automations (or Utilities in a classic layout)
Before you begin
Identify the business purpose, approved destination and data owner. Review your organisation’s privacy requirements and the connected providers’ terms before sharing personal information.
Follow these steps
- Confirm the company workspace and authorising staff account before consent.
- Review the lead fields that the connector can return or send. Treat names, contact details, address and descriptive notes as potentially sensitive.
- Map only the information needed by the destination and restrict access to the Zap and destination account.
- Use fictional or minimised test data and keep passwords, codes, tokens and private customer information out of support evidence.
- Agree retention and removal responsibilities in the CRM, Zapier and destination systems, then review access during staff changes.
Check the result
The team knows which workspace and providers receive information, why the data is needed and who is responsible for access and retention.
If something does not look right
If a connection or secret may have been exposed, pause affected automation and contact the administrator or support through the established security process. Do not copy the secret into another message to demonstrate the problem.
Fields, rules and limits
- The API returns a defined set of lead fields, and event payloads can include those fields even if a later Zap step maps only some of them.
- Tenant selection is established by the connected workspace, not by an arbitrary caller-supplied company parameter.
- Connector event and audit retention is not a substitute for your business record-retention policy or a complete export of Zapier history.
Questions and answers
Which information can a lead event contain?
The payload can include lead identity, name, title, company, description, location/address, assignment, status/source and labels, timestamps, creator reference, email, website and phone. Review the approved payload before live use.
Does mapping fewer fields mean Zapier never receives the other fields?
Not necessarily. The connector can send a fuller lead event to Zapier before a later action maps selected fields to its destination.
Does connecting make the CRM publicly readable?
The documented lead and identity endpoints require an authorised connection. Keep those credentials private and grant only the access appropriate to the workflow.
Is this automatically GDPR compliant?
A connector does not by itself determine compliance. Your organisation must establish the purpose, lawful handling, provider arrangements, access and retention appropriate to its use.
Where is the data physically processed?
Processing depends on your CRM hosting and the Zapier/destination services you choose. Obtain the relevant provider information and agreement rather than inferring residency from a product name.
Can I use ordinary notes for API secrets?
No. Keep credentials in the approved connection mechanism, not CRM notes, spreadsheet cells, screenshots or help requests.
Does revoking access erase data already sent?
No. Manage records and retention in each receiving system separately under your organisation’s policy.
Useful next steps
- Resolve Zapier connection and lead errors
- Check supported actions and operating limits
- Prepare a useful Zapier support request
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.