Zapier

The Zapier activity triggers a Zapier Zap by sending a POST request to a Zapier webhook URL with a set of named properties.

Purpose

Use the Zapier activity to:

• Trigger any Zap that starts with a Webhooks by Zapier trigger
• Pass dynamic data from the workflow context to the Zap as properties
• Integrate Una workflows with thousands of apps connected via Zapier

Prerequisites

A REST API data source must be configured in Una pointing to the Zapier webhook base URL. Zapier webhook URLs typically look like:

https://hooks.zapier.com/hooks/catch/<account-id>/<hook-id>/

Configure the full base URL in the data source. The Zapier activity sends a POST to the root path of that data source.

Configuration

Data Source

Select the REST API data source configured with the Zapier webhook URL. Only REST API data sources are available.

Properties

Key/value pairs included as fields in the JSON body sent to the Zap. Both key and value support interpolation.

Field	Description
Name	The property name (becomes a field in the Zapier trigger payload)
Value	The value — static or interpolated from the workflow context

Example:

entity    = {{var:EntityName}}
period    = {{var:Period}}
amount    = {{var:TotalAmount}}
triggered = {{ctx:today}}

Zapier receives:

{
  "entity": "EMEA",
  "period": "2025-Q1",
  "amount": "1234567",
  "triggered": "2025-05-08"
}

Behavior

1. Properties are assembled into a JSON object.
2. A POST request is sent to the data source base URL.
3. If the response is a success (2xx), the activity returns Success.
4. If the response is not a success, the activity throws an exception and returns Error.

The Zapier activity always uses POST. Unlike the generic Rest API Call activity, there is no verb or path field — the entire URL is taken from the data source.

Usage Notes

• Zapier webhooks accept any JSON structure. The property names you define here become the field names available in your Zap.
• Zapier's free plan limits the number of tasks per month. For high-frequency workflows, verify your Zapier plan.
• The activity does not wait for the Zap to finish — it only confirms that Zapier accepted the webhook. If the Zap itself fails, that is visible only in the Zapier dashboard.

Best Practices

• Name properties to match the field names your Zap expects. Changes to property names require updating both the Una workflow and the Zap.
• Store the Zapier webhook URL in the data source, not hardcoded anywhere else, so it can be rotated without touching workflows.
• Test the Zap manually with the Zapier webhook tester before using it in a production workflow.

JSON Reference

{
  "discriminator": "ZappierWorkflowActivity",
  "activityId": "<uuid>",
  "name": "Zapier",
  "positionX": 0,
  "positionY": 0,
  "advanceRule": 2,
  "dataSource": "MyZapierWebhook",
  "properties": [
    { "key": "entity", "value": "{EntityName}" },
    { "key": "period", "value": "{Period}" }
  ]
}

Property	Type	Description
dataSource	string	Corresponds to the Data Source field. The REST API data source configured with the Zapier webhook base URL.
properties	array	Corresponds to the Properties list. Array of { "key": string, "value": string } objects assembled into the JSON body sent to the Zap. Both key and value support {variable} interpolation.