Skip to main content
You can automatically send leads from another app into Z360 using Zapier. For example, a new lead comes in from Facebook Lead Ads, Typeform, Excel, or Calendly, and Zapier creates an inquiry in your Z360 pipeline — no code required. Z360 has a dedicated Zapier app (invite-only). You do not need to build custom webhook requests — the Z360 app handles request formatting for you.
Before you start, make sure your inquiry pipeline is created, saved, and active. You will also need the pipeline Endpoint URL and Organization API Key from Z360. To get these, go to Settings → Product → Inquiries, open the pipeline menu (three dots), click Generate Link, and open the API tab.

Step 1: Create a New Zap

  • Log in to zapier.com.
  • Click Create Zap (or + Create → Zaps).

Step 2: Set Up the Trigger

The trigger is the app that sends the lead.
  • Search for and select your trigger app (e.g., Excel, Facebook Lead Ads, Typeform, Calendly).
  • Choose the trigger event (e.g., “New Row”, “New Lead”, “New Entry”).
  • Connect your account for that app if prompted.
  • Select the specific spreadsheet, form, page, or event you want to use.
  • Click Test trigger and confirm Zapier pulls in a sample record.

Step 3: Add Z360 as the Action

  • Click the + button to add an action step.
  • Search for Z360.
  • Select Z360 (1.0.0) — it will show as “Invite Only”.
  • Choose Create Inquiry as the action event.
  • Click Continue.
Connect Your Z360 Account When prompted, Zapier opens a popup where you need to enter two things:
  • API Key — Paste the Organization API Key (Bearer Token) you copied from Z360.
  • Platform — Select which Z360 environment to use (e.g., beta or staging). Most users should select beta.
Click Yes, Continue to save the connection. Once connected, you can reuse this account for future Zaps. If you have already connected your Z360 account, select it from the dropdown and click Continue.

Step 4: Configure the Inquiry Fields

Zapier shows you the following fields to fill in: Endpoint (required) Paste the pipeline endpoint URL you copied earlier (e.g., https://beta.z360.biz/forms/{id}/api). Inquiry Fields (required) Map each field from your trigger app to the corresponding Z360 field:
Z360 FieldWhat to Map
First NameSelect the first name field from your trigger app
Last NameSelect the last name field from your trigger app
EmailSelect the email field from your trigger app
Phone NumberSelect the phone number field from your trigger app
Click inside each field and Zapier shows a dropdown of available data from your trigger app. Select the matching value. If your pipeline has additional custom fields, they may also appear here. Map them the same way. Consent (optional) If your pipeline has consent enabled, set this to True. If consent is not required on your pipeline, you can leave this blank or set it to False.

Step 5: Test the Zap

  • Click Test step.
  • Zapier sends a real request to Z360 using the sample data from Step 2.
  • Check that the test succeeds in Zapier.
  • Open Z360 and confirm the inquiry appears in the correct pipeline with the correct data.
If the test fails, see the Troubleshooting section below.

Step 6: Publish the Zap

Once the test passes, click Publish to activate the Zap. From now on, every new record from your trigger app will automatically create an inquiry in Z360.

Troubleshooting

  • Z360 account connection fails — Make sure you have been invited to the Z360 Zapier app. Contact your Z360 administrator if you cannot connect your account.
  • Test returns an error about missing fields — Check that all four required fields (First Name, Last Name, Email, Phone Number) are mapped. If any field is left empty or unmapped, the inquiry cannot be created.
  • Phone number rejected — The phone number must be a valid US phone number with country code. Format: +15555555555. If your trigger app sends numbers like (555) 555-5555, add a Zapier Formatter step between the trigger and the Z360 action to reformat the phone number.
  • Duplicate lead not created — Z360 blocks duplicate submissions for the same pipeline when the same email has already been submitted. This is expected behavior, not an error.
  • Test passes but live Zap does not work — Check that the Zap is published and turned on. Also check that the trigger app is sending data in the same format as the test sample.
  • Inquiry appears in the wrong pipeline — Double-check the Endpoint URL in the Configure step. Each pipeline has a unique endpoint. Make sure you copied the URL for the correct pipeline.
  • Zap fails with an authentication or unexpected error — Check that the pipeline’s communication channel is still configured in Z360. If someone removes or changes the communication channel on the pipeline, the Zap may fail even if the API key and fields are correct. Go to Settings → Product → Inquiries, open the pipeline, and make sure it has an active communication channel assigned.

Quick Summary

  1. Get your pipeline Endpoint and API Key from Z360: Settings → Product → Inquiries → Generate Link → API.
  2. Create a Zap with your lead source app as the trigger.
  3. Add Z360 → Create Inquiry as the action.
  4. Connect your Z360 account (API Key + Platform).
  5. Paste the pipeline Endpoint URL.
  6. Map First Name, Last Name, Email, and Phone Number from your trigger app.
  7. Set Consent to True if required by your pipeline.
  8. Test, verify in Z360, and publish.

Tips

  • Start with one pipeline only. Add more after the first one works.
  • Test with your own email and phone number first before connecting live data.
  • Copy field names exactly — do not type them from memory.
  • Confirm the inquiry appears in the correct pipeline after each test.
  • Prepend +1 if your source sends phone numbers without country codes before they reach Z360.
  • Save a screenshot of your working configuration for your team.