Skip to main content
Yes. Each pipeline has its own unique endpoint URL. Set up a separate integration (API request or Zap) for each pipeline using that pipeline’s specific endpoint. Do not reuse the same endpoint for different pipelines.
No. The Zapier method is fully no-code. You just need your pipeline endpoint URL and Organization API Key from Z360, and then you map fields using Zapier’s visual interface. The API method is the one that may require a developer or someone comfortable with HTTP requests.
Z360 blocks duplicate submissions within the same pipeline. If the same email address has already been submitted to that pipeline, the second submission will not create a new inquiry. This is expected behavior and helps prevent duplicate leads.
Yes. If your pipeline’s inquiry form has custom fields, include them inside form_data (for API) or map them in the Zapier action step. Use the exact field name as shown in your inquiry form — Z360 matches custom field names by lowercasing both sides.
Yes. The Zapier integration uses the same Organization API Key. If you revoke the key, all integrations using it — both API and Zapier — will stop working immediately. Have the new key ready to update everywhere before revoking.