Where to start
CRM workspace → Tools → Britixo Automations (or Utilities in a classic layout)
Before you begin
Pause repeated write attempts if a lead or destination action may already have completed. Preserve references rather than reproducing the problem repeatedly on live information.
Follow these steps
- State the workspace’s public base URL and the company you intended to use.
- Identify the Zap, affected step and whether the operation was connection, search, create, subscription or event delivery.
- Provide the time with timezone, exact visible error and the Zap run reference. Include a request reference if the app returned one.
- List the relevant CRM lead ID and destination record ID, plus whether each record actually exists.
- Describe the expected result, the observed result, recent account/permission changes and the safe checks already completed.
- Use the Proplix contact or support route. Redact secrets and minimise personal information before attaching evidence.
Check the result
Support can identify the workspace, operation and affected records without needing a password, a token or a live customer’s full data.
If something does not look right
If you only have a generic error, include the time, company, action and run reference. Do not paste browser cookies, raw authorisation headers or a complete customer export.
Fields, rules and limits
- Useful evidence includes workspace URL, Zap/run references, lead/destination IDs, time, message and expected outcome.
- Never provide passwords, verification codes, OAuth authorisation codes, access/refresh credentials or client secrets.
- Say whether the Zap is paused and whether an uncertain write may already exist.
Questions and answers
Do I need to understand API terminology?
No. Describe what you clicked, which company you used, what you expected and what appeared. The visible error and run reference are often enough to start.
Should I send a screen recording?
Only if useful and appropriately redacted. Avoid recording sign-in, verification, private notes, personal data or connection credentials.
What timezone should I use?
Include the timezone shown with your recorded time. If comparing CRM, Zapier and destination histories, state which clock each time came from.
Should I include the full lead information?
Usually IDs and a minimised description are sufficient. Share more personal information only through the approved process when support establishes that it is needed.
Can support tell whether a timeout created a record?
The relevant CRM ID, destination reference, run reference and time help support correlate evidence. Do not assume a timeout means the write failed.
Should I disable unrelated Zaps?
Identify and pause the affected workflows or overlapping sources. Avoid broad changes that disrupt unrelated business processes.
Useful next steps
- Check supported actions and operating limits
- Zapier connector API reference for integrators
- Zapier Ready Integration: common client questions
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.