Skip to main content
The Organization API Key is either missing, incorrect, or formatted wrong in the request header. Go to Settings → Product → Inquiries, open your pipeline menu, click Generate Link → API, and copy the key again. Make sure the Authorization header reads exactly Bearer YOUR_API_KEY with a single space between “Bearer” and the key, and no trailing spaces or line breaks.
First, confirm the Zap is published and turned on in your Zapier dashboard. Then check that the trigger app is still sending data in the same format as the test sample — if your trigger app changed its field structure or output format, the mapped fields may no longer match. Re-test the trigger step to pull a fresh sample, then re-map the fields if needed.
Check that the pipeline’s communication channel is still configured. If someone removes or changes the communication channel on the pipeline, integrations will fail even if the API key and field names are correct. Go to Settings → Product → Inquiries, open the pipeline, and make sure it has an active communication channel assigned.
Z360 requires phone numbers in E.164 format with the country code — for example, +15555555555. If your source app sends numbers in formats like (555) 555-5555 or 555-555-5555, you need to reformat them before they reach Z360. For Zapier, add a Formatter step between the trigger and the Z360 action to prepend +1 and strip special characters.
The integration is sending a field name that does not exist in the pipeline’s inquiry form. Go to your pipeline’s inquiry form and check the exact field names — then update your integration to match. Field names are case-insensitive, but must match the spelling and format shown in the form. Do not type field names from memory — always copy them directly.