Zapier

Use Zapier to automate workflows between Hiveality and your other tools.

Open the dialog

Connect Zapier

1. Reveal your Website API Key. Reveal Website API Key
2. Install the Hiveality Zapier app using the invite link.
3. Confirm webhook endpoints are active if you are using triggers. Webhooks

Connected accounts in Zapier are labelled with the business name, website name, or website slug from the API key test response, which makes it easier to pick the right site when you manage multiple Zaps.

Optional: Webhooks by Zapier

If you want to send manual requests from Zapier, use the API base URL shown in the dialog.

Dynamic field pickers

Some Zapier actions can populate IDs from Hiveality so you do not have to copy and paste them manually.

• Order fields can show recent orders.
• Product fields can show products.
• Social review reply fields can show recent reviews that still need a reply.

You can still paste an ID when you need an item that is not in the dropdown.

Filter order triggers by product

The Order Created and Order Paid triggers can watch selected products:

1. Add either order trigger to a Zap.
2. In Products, choose one or more products from the picker.
3. Leave the field blank when the Zap should run for every product.

An order that contains any selected product can start the Zap. During trigger testing, Zapier loads recent matching order events when available. If no match was recorded in the last 30 days, the test result is clearly labeled as sample data; run a new test checkout and check Zap History before turning on a fulfillment or access workflow.

Filter tag and form triggers

The Contact Tag Added, Contact Tag Removed, and Form Submitted triggers also have searchable multi-select pickers:

1. Choose one or more Tags or Forms in the trigger setup.
2. Leave the picker blank to trigger for every tag or form.
3. Add or remove the selected tag, or submit the selected form.
4. Select Test trigger to load up to three matching events from the last 30 days.

Hiveality applies this filtering before sending the event to Zapier, so a separate Zapier Filter step and copied UUIDs are not required. Multiple selections use match-any behavior.

Form Submitted records include the form name, public and internal form IDs, submission ID, contact details, and the submitted values under

Submitted Form Fields. If no recent event exists, Zapier returns a record clearly marked as sample data.

Phone numbers in Upsert Contact

The Upsert Contact action treats phone as optional and helps keep contact automations moving:

• Common 10-digit United States and Canada formats are normalized automatically.
• International numbers should begin with +, 00, or 011.
• If an optional phone cannot be normalized, Zapier skips that value, reports a phone warning in the successful action output, and still completes the contact, tag, and list updates.
• A skipped phone never clears a valid phone already saved on the contact.

Addresses in Upsert Contact

The Upsert Contact action can also send optional contact address details:

• Street Address
• City
• State / Province
• ZIP / Postal Code
• Country

You can send only the fields you have. Blank address inputs are left out of the update, so a partial Zap does not erase address details already saved on the contact.

Common Zapier uses

• Create or update contacts, tags, lists, and email preferences from another app.
• Create blog post drafts, attach tags/categories, and publish or schedule posts after review.
• Create emails, send test emails, duplicate campaign drafts, and pull campaign metrics or recipient logs.
• Import images, documents, and videos from public URLs into the file or video library — and continue the workflow once Mux finishes preparing the video.
• Update product titles, descriptions, images, and SEO from another app.
• Use webhook triggers when another tool should react to leads, forms, contact updates, subscriber list changes, booking events, commerce updates, access changes, video readiness, course or product publish events, or community moderation activity.
• Filter Order Created or Order Paid triggers when a Zap should react only to purchases containing selected products.
• Use board/card, community event, and member activity triggers when a Zap should react to pipeline movement, new events, or new member joins.

Keep Zapier aligned with Hiveality

Use Webhooks for the current event list and Reveal Website API Key for API actions. The Hiveality Zapier app is refreshed as new content, commerce, learning, and community actions become available.