Resolve Zapier connection and lead errors
Work through Pixie CRM Zapier workspace, authorisation, validation, rate-limit and delivery errors using safe checks and useful support evidence.
Before you begin
Capture the exact visible message, affected action, time with timezone and workspace URL. Remove credentials and private customer details from any screenshot.
CRM workspace → Tools → Pixie CRM Automations (or Utilities in a classic layout)
Follow these steps
- For an unavailable app or missing menu, verify module availability, the approved app access route and the administrator’s workspace.
- For invalid_workspace, use the confirmed HTTPS base URL rather than a marketing, MyAccount or individual admin-page address.
- For authentication or permission errors, test the selected company connection and review the authorising staff account’s active status and lead permissions.
- For validation errors, inspect the required name, email, staff assignment and mapped source/status values.
- For rate limits, wait and reduce bursts. For server or timeout errors, inspect existing records before replaying a write and escalate persistent failures.
Check the result
You have either corrected a specific cause and verified the result, or paused the workflow with enough non-sensitive evidence for support to investigate.
Rules, fields and operating limits
- HTTP 401 indicates an unusable token or missing required permission in this API.
- HTTP 422 indicates validation failure; 404 indicates a missing resource, unavailable route or disallowed broker context.
- HTTP 405 indicates the wrong method, 429 indicates a rate limit, and 5xx indicates a service-side or upstream failure.
- The API can return a request reference in X-Britixo-Request-Id for support correlation.
If something does not look right
Avoid repeatedly reconnecting, changing company URLs or resending create actions without checking the actual error and resulting records. Different failure types need different remedies.
Questions and answers
What does invalid_workspace mean?
The supplied base URL was not accepted as an active registered workspace. Check HTTPS, the company address and the absence of page/query components with support.
What does invalid_grant mean?
An authorisation code or refresh credential was invalid, expired, already used or could not satisfy the required flow. Restart the approved connection process when directed; do not paste codes into support.
What does invalid_token mean?
The token may be missing, expired, revoked or insufficiently authorised for the operation. Test the correct connection and review staff permissions.
What does HTTP 429 mean?
A rate limit was reached. Allow time before retrying and reduce bursts. Do not create multiple connections merely to bypass the limit.
What should I do after HTTP 500, 502 or 503?
Preserve the reference and time, check whether a write already completed and pause repeated write attempts. Contact support if the failure persists.
Why do I get 404 for a lead I can see elsewhere?
Check the company connection and lead ID. IDs are local to a workspace; a lead from another company is not available through this connection.
Why do I get 405?
The request method is not supported at that endpoint. In a standard Zap, ask support or the app integrator to check the app configuration instead of editing methods at random.
Why does a successful action save the wrong status?
An invalid or unmapped source/status can fall back to an available value. Choose valid workspace options and compare the saved record with your intended mapping.
Why is the connector page healthy but my Zap fails?
Health checks demonstrate basic endpoint availability. They do not prove your account permission, subscription, field mapping, destination connection or later Zap steps.
Can support investigate without my token?
Yes. Provide the workspace, Zap/run reference, action, time, public error and relevant record IDs. Never include OAuth secrets or authorisation headers.
Useful next steps
Contact Pixie CRM support. Include the workspace, action, run reference and time; keep credentials private.