Skip to main content
Bit Integrations is a free WordPress automation plugin that connects form builders to external services via webhooks — no code, no external middleware like Zapier required. It runs entirely on your WordPress site. Use this method when your form builder cannot connect to Z360 natively — for example, Elementor Forms, JetFormBuilder (for Pipelines), Formidable Forms, Forminator, Divi, Beaver Builder, and many others. Bit Integrations captures the form submission, lets you map fields and set custom headers, then sends the data to Z360 in the exact format it expects.
If your form builder already supports webhooks natively with custom headers and field mapping (e.g., Gravity Forms, WPForms, Fluent Forms, CF7), you can connect directly without Bit Integrations. See Connect Z360 with WordPress Plugins.

​
What You Need

  • The Bit Integrations plugin installed and activated.
  • Your form builder plugin installed with at least one form created.
  • Your Z360 endpoint credentials — see Z360 Endpoints below.
Free vs Pro: Bit Integrations’ free version supports triggers from Elementor Forms, Contact Form 7, WPForms, and a few others. Most other form builders (JetFormBuilder, Formidable, Forminator, Gravity Forms, Fluent Forms, Ninja Forms, Divi, Everest Forms, etc.) require Bit Integrations Pro.

​
Z360 Endpoints

Z360 provides two types of endpoints. Both accept flat JSON. Forms (Webhook URL — no auth required):
  • URL: https://app.z360.biz/webhooks/forms/z360_{uuid}
  • Header: Content-Type: application/json
  • Field names: first_name, last_name, email, phone
  • Found in: Z360 → Forms → select form → Generate Form Links → Webhook section
Pipelines (API Endpoint — Bearer auth required):
  • URL: https://app.z360.biz/forms/{id}/api
  • Headers: Content-Type: application/json and Authorization: Bearer {your_token}
  • Field names: First Name, Last Name, Email, Phone Number
  • Found in: Z360 → Pipelines → select pipeline → three dots → Generate Link → API / Webhook tab
For Pipelines, the pipeline’s communication channel must be enabled. If disabled, the API endpoint will redirect to the Z360 homepage and no lead will be created.

​
How It Works

Every Bit Integrations flow has two parts:
  1. Trigger — select your form builder and form (different per plugin).
  2. Action — configure the outgoing webhook to Z360 (same for all plugins).
The trigger setup varies slightly per form builder. The action setup is identical regardless of which form you use.

​
Step 1: Select Your Trigger

Open Bit Integrations → Create Integration and select your form builder from the trigger list.
  • Select Elementor from the trigger list.
  • Choose your Elementor form from the dropdown.
  • Click Fetch to pull in the form fields.
  • Submit a test entry through the form on the live page so Bit Integrations can capture the field data.
  • Verify that the captured fields appear (First Name, Last Name, Email, Phone, etc.).
  • Click Next.
Elementor Forms require Elementor Pro. The Bit Integrations trigger for Elementor is available in the free version of Bit Integrations.
  • Select Contact Form 7 from the trigger list.
  • Choose your form from the dropdown.
  • Click Fetch to pull in the form fields.
  • Submit a test entry to capture the field data.
  • Verify the captured fields and click Next.
  • Select WPForms from the trigger list.
  • Choose your form from the dropdown.
  • Click Fetch to pull in the form fields.
  • Submit a test entry to capture the field data.
  • Verify the captured fields and click Next.
  • Select JetFormBuilder from the trigger list.
  • Choose your form from the dropdown.
  • Bit Integrations will generate a webhook URL — copy it.
  • In the JetFormBuilder editor, add a Call Webhook post-submit action and paste the Bit Integrations webhook URL.
  • Submit a test entry to capture the fields.
  • Return to Bit Integrations and verify the captured fields appear.
  • Click Next.
  • Select Formidable Forms from the trigger list.
  • Choose your form from the dropdown.
  • Click Fetch to pull in the form fields.
  • Submit a test entry to capture the field data.
  • Verify the captured fields and click Next.
  • Select Forminator from the trigger list.
  • Choose your form from the dropdown.
  • Click Fetch to pull in the form fields.
  • Submit a test entry to capture the field data.
  • Verify the captured fields and click Next.
  • Select Gravity Forms from the trigger list.
  • Choose your form from the dropdown.
  • Click Fetch to pull in the form fields.
  • Submit a test entry to capture the field data.
  • Verify the captured fields and click Next.
  • Select Fluent Forms from the trigger list.
  • Choose your form from the dropdown.
  • Click Fetch to pull in the form fields.
  • Submit a test entry to capture the field data.
  • Verify the captured fields and click Next.
  • Select Ninja Forms from the trigger list.
  • Choose your form from the dropdown.
  • Click Fetch to pull in the form fields.
  • Submit a test entry to capture the field data.
  • Verify the captured fields and click Next.
  • Select Divi from the trigger list.
  • Choose your Divi contact form from the dropdown.
  • Click Fetch to pull in the form fields.
  • Submit a test entry to capture the field data.
  • Verify the captured fields and click Next.
  • Select Everest Forms from the trigger list.
  • Choose your form from the dropdown.
  • Click Fetch to pull in the form fields.
  • Submit a test entry to capture the field data.
  • Verify the captured fields and click Next.
  • Select Beaver Builder from the trigger list.
  • Choose your form module from the dropdown.
  • Click Fetch to pull in the form fields.
  • Submit a test entry to capture the field data.
  • Verify the captured fields and click Next.
  • Select Brizy from the trigger list.
  • Choose your form from the dropdown.
  • Click Fetch to pull in the form fields.
  • Submit a test entry to capture the field data.
  • Verify the captured fields and click Next.
  • Select Happyforms from the trigger list.
  • Choose your form from the dropdown.
  • Click Fetch to pull in the form fields.
  • Submit a test entry to capture the field data.
  • Verify the captured fields and click Next.
Bit Integrations supports 50+ form builders including WS Form, Kadence Blocks Form, SureForms, Tripetto, ARForms, eForm, FormCraft, Gutena Forms, and more. The trigger setup is the same for all: select the plugin, select the form, fetch fields, submit a test entry, and click Next.For the full list of supported triggers, see the Bit Integrations trigger directory.

​
Step 2: Configure the Webhook Action

After selecting your trigger and clicking Next, you’ll see the action selection screen. Select Webhook (listed under the actions). The webhook configuration is the same regardless of which form builder you selected in Step 1. Choose the option that matches where you want the lead to go.
Webhook URL: Paste your Z360 Webhook URL.Method: POSTHeaders: Add one header row:Body: Check “Send All Data” or use field mapping to map specific fields:Click Test Webhook to send a test request. Check Z360 to confirm the lead appeared. If successful, click Save & Finish.
Webhook URL: Paste your Z360 API Endpoint URL.Method: POSTHeaders: Add two header rows:Replace z360_your-token-here with the actual token from Z360’s API / Webhook tab.Body: Use field mapping to map specific fields:Click Test Webhook to send a test request. Check Z360 to confirm the lead appeared in the correct pipeline. If successful, click Save & Finish.

​
Supported Form Builders

Bit Integrations supports triggers from the following form builders. The webhook action (Z360 connection) works the same for all of them. For the complete list of 50+ supported triggers, see the Bit Integrations directory.

​
Tips

  • Test with a real phone number with country code. Z360 validates phone numbers and rejects fake or test numbers.
  • Always copy field names and endpoint URLs directly from Z360 — do not type from memory.
  • Use Bit Integrations’ built-in Test Webhook button before saving. It confirms the connection works without needing to resubmit the form.
  • Each integration has a timeline log — use it to check success or error status after live submissions.
  • You can create multiple integrations for the same form — for example, one sending to a Z360 Form and another sending to a Z360 Pipeline.

​
Frequently Asked Questions

The free version supports triggers from Elementor Forms, Contact Form 7, WPForms, Bit Form, and a few others, with unlimited active integrations and the outgoing webhook action. Most other form builders require Bit Integrations Pro.
Bit Integrations runs entirely on your WordPress site — no external service, no monthly fees beyond the plugin, no data leaving your server until it reaches Z360. Zapier is a cloud service that acts as middleware between platforms. If you’re already on WordPress, Bit Integrations is simpler and more cost-effective.
Yes. Bit Integrations operates independently. If you already have a native webhook set up (e.g., Gravity Forms to Z360 via the Webhooks addon), Bit Integrations won’t interfere. You can use both simultaneously or replace one with the other.
Yes. Z360 validates phone numbers and expects them with a country code (e.g., +1 for US).
Yes. Add more rows in the body field mapping. For Forms, use snake_case field names. For Pipelines, use the exact field name as shown in Z360’s API tab.
Possibly. Bit Integrations also supports a Custom Trigger (Pro) that works with any plugin via a custom do_action hook, and an Incoming Webhook trigger that accepts data from any source. Check the trigger directory for the full list.

​
Troubleshooting

For Pipelines, check that the pipeline’s communication channel is enabled. For Forms, verify the Webhook URL matches exactly what Z360 shows. Also confirm the field names are correct — first_name (snake_case) for Forms, First Name (Title Case) for Pipelines.
A required field is missing or a field name does not match. Check spelling, casing, and spacing of all field keys. Phone numbers must be real and include a country code.
Pipelines only — the Bearer token is incorrect or missing. Copy it again from Z360’s API / Webhook tab. Make sure the Authorization header value is exactly Bearer z360_your-token-here with a single space after “Bearer”.
Make sure you submit a test entry through the live form after setting up the trigger in Bit Integrations. The plugin listens for real submissions to capture the field structure. Also verify the form builder plugin is active and the form is published.
Open the integration’s Timeline in Bit Integrations to see the full error response. Common causes: expired or revoked Bearer token, Z360 form deleted, pipeline communication channel disabled, or field names changed in Z360 after initial setup.
📖 Related articles: