List the campaign link click is associated with.

List that the contact note is associated with.

List the subscriber is updated in.

Leave blank to trigger for all Tags, begin typing to filter, or use the Custom tab for text/input entry

Suggested Format: https://www.example.com

In dollars. Example: 350.00.

The "Auto" option only works if your chosen pipeline has "Automatic Deal Assignment" configured. If no value (or invalid value) is supplied, it will default to the connected ActiveCampaign account user.

Example: usd.

The contact will be removed from this automation.

The automation run(s) that the contact will be removed from.

ActiveCampaign ID of the contact.

Contact that will get added to the account.

Choose an account.

Set a job title for the related contact.

The ID of the Contact where the tag will be added or removed

Add or remove tag from AC Contact

Choose from list or enter/insert tag data below

Enter/insert tag data or use the drop down list above, separate tags with a comma

The object that you want to create a record for in ActiveCampaign

To update an existing record, provide the record ID or external ID

To update an existing record, provide the record ID or external ID

In cents. Example: $350.00 would be 35000.

The "Auto" option only works if your chosen pipeline has "Automatic Deal Assignment" configured. If no value is supplied, it will default to the connected ActiveCampaign account user.

Example: usd.

An Account or Contact is required to create a deal.

An Account or Contact is required to create a deal. The Contact selected will be made the Primary Contact.

Deal's description

Insert the task ID to be updated. Leave blank if creating a new task.

The title to be assigned to the task.

Insert the ID of the Deal to be assigned this task.

The content describing the task.

Due date of the task ex. 2021-02-25T12:00:00-06:00.

End Date (i.e. duration) of the task ex. 2021-02-25T12:15:00-06:00. Must be later than Due Date.

The type of the task based on the available Task Types in your account.

The id of the user this task will be assigned to.

Subscribing will not update lists the Contact already belongs to with any status. Unsubscribing requires the contact already belongs to the list in some status.

List from which you'd like to your Contact to be Subscribed/Unsubscribed

ActiveCampaign ID of the Contact. NOTE: IF THIS IS NOT PROVIDED, 'Email Address' MUST BE

Email of the Contact. NOTE: IF THIS IS NOT PROVIDED, 'Contact ID' MUST BE

The contact task title

The related contact ID

The title of the Deal

The email of a Contact on the Deal

Email of the user being searched

The HTTP method we'll use to perform the request.

Any URL with a querystring will be re-encoded properly.

If yes, request data below will be overridden with the raw data from the previous step (you are still responsible for headers though, like Content-Type). Defaults to no.

Place raw data for the request here. Could be JSON, XML, etc. Nothing is parsed for you here (including extra line breaks or spaces -- everything is sent verbatim). You probably need to define a header below corresponding to your data Content-Type. Reminder: data provided in this field is completely ignored if you chose "yes" to pass-through.

By default we convert fields with double underscores into nested dictionaries. Select no here to turn this behavior off.

A pipe (|) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.

Any URL with a querystring will be re-encoded properly.

Pay special attention to the proper mapping of the data below.

These are key-value pairs that will form the data portion of the request. If you leave these empty, all fields from the previous step will be used. If you want to send your own raw JSON or form-encoded values here, please use the Custom Request action instead.

Wraps the request in an array if that is something the service requires.

A file object to be attached to the request. The request will automatically be converted to multipart/form-data, with the above payload type defining the sub content-type for the data being passed.

By default we convert fields with double underscores into nested dictionaries. Select no here to turn this behavior off.

A pipe (|) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.

List the campaign bounce is associated with.

List the campaign open is associated with.

Leave blank to trigger for all task types, begin typing to filter, or use the Custom tab for text/input entry.

List the subscriber is added to.

Adding contacts to lists via the CSV importer will not cause this trigger to fire.

List the subscriber is added or updated in. Leave blank if you wish this trigger to run on all contact adds or updates.

Choose "Yes" to stop unsubscribe events from triggering the zap.

Creating contacts via the CSV importer will not cause this trigger to fire.

Suggested Format: https://www.example.com

ActiveCampaign ID of the contact. NOTE: IF THIS IS NOT PROVIDED, 'email' MUST BE

Email of the contact, once created it cannot be updated via this action. NOTE: IF THIS IS NOT PROVIDED, 'id' MUST BE.

Only use this if you can't obtain the first and last name fields separately.

Can be used with our SMS feature.

Separate multiple tags with a comma (IE: "tag1, tag2, etc").

Job Title will be available when there is an Account associated.

The contact email address (to add into the automation).

The email message (previously created). No HTML/text values accepted here. To generate a new email message, create a new campaign and set up the email message on the template step. Save it, then come back into Zapier and choose that message from the dropdown here.

This is internal name of the campaign, not the subject.

Enter the contact ID.

Enter the List ID or enter zero for all lists.

Insert the task ID to be updated. Leave blank if creating a new task

The title to be assigned to the task.

Insert the ID of the Contact to be assigned this task.

The content describing the task.

Due date of the task ex. 2021-02-25T12:00:00-06:00.

End Date (i.e. duration) of the task ex. 2021-02-25T12:15:00-06:00. Must be later than Due Date.

The type of the task based on the available Task Types in your account.

The id of the user this task will be assigned to.

In cents. Example: $350.00 would be 35000.

Example: usd.

Deal's description

Found under the Settings > Tracking > Event Tracking section of ActiveCampaign.

Found under the Settings > Tracking > Event Tracking API section of ActiveCampaign.

If not supplied the event will still be saved.

ActiveCampaign ID of the contact. NOTE: IF THIS IS NOT PROVIDED, 'email' MUST BE

Email of the contact. NOTE: IF THIS IS NOT PROVIDED, 'id' MUST BE

Use either Deal Title or Contact Email to search for a deal. If both are filled out, both the title and email must match on a deal to get a result.

Use either Deal Title or Contact Email to search for a deal. If both are filled out, both the title and email must match on a deal to get a result.

The deal task title

The related deal ID

This should return a list of dictionaries of content type JSON in reverse chronological order. For example: [{"id":1234},{"id":1235}]

If the returned JSON is not a list and is instead an object (maybe paginated), enter the key that contains the results. Example: "results", "items", "objects", etc... (children via dot syntax supported)

Zapier deduplicates the array we see each poll against the id key. If the id key does not exist, you should specify an alternative unique key to deduplicate off of. If neither are supplied, we fallback to looking for the shortest key with id in it otherwise we will raise an error.

If the content fetched is XML or HTML, optionally define an xpath to extract data from the content. Will trigger whenever the content at the xpath changes!

A pipe (|) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.

By default, Zapier gives you the entire payload of the webhook. If this is specified, Zapier will only grab the child key from the object(s) sent to Zapier. For example, given {"contact": {"name": "Mike"}}, add "contact" here to only return {"name": "Mike"}. Traverse more deeply nested children by using dot-separated syntax. Line item payloads will run your Zap for each instance of the child key.

We recommend not putting any query string arguments in the URL (use "Query String Params" below).

These params will be URL-encoded and appended to the URL when making the request. Note: If you specify nothing for this field, we will automatically encode and include every field from the previous step in the query string. If you don't want this, use the "Custom Request" action.

If "yes", this dumps the results directly to a key (set below) as JSON. If "no", we simulate a form.

Only used if As JSON.

By default we convert fields with double underscores into nested dictionaries. Select no here to turn this behavior off.

A pipe (|) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.

Any URL with a querystring will be re-encoded properly.

Pay special attention to the proper mapping of the data below.

These are key-value pairs that will form the data portion of the request. If you leave these empty, all fields from the previous step will be used. If you want to send your own raw JSON or form-encoded values here, please use the Custom Request action instead.

Wraps the request in an array if that is something the service requires.

A file object to be attached to the request. The request will automatically be converted to multipart/form-data, with the above payload type defining the sub content-type for the data being passed.

By default we convert fields with double underscores into nested dictionaries. Select no here to turn this behavior off.

A pipe (|) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.