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

Determines which App Extensions will appear in the dropdown below.

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

Determines which App Extensions will appear in the dropdown below.

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 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.

API docs for ActiveCampaign are located here https://developers.activecampaign.com/v3/reference

Requests can only be made to domains associated by this application.

These params will be URL-encoded and appended to the URL when making the request.

Authentication headers are included automatically

Zapier will apply these optional headers and values to the request in addition to any headers created as part of the authentication mechanism.

Zapier will pass this along raw. If you would like to provide complex JSON, try a "Code by Zapier" step to build the structure and pass it along here. For example, {"foo": "bar"} is perfectly valid.

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

Maximum of 10 characters that may only contain[a-z A-Z 0-9 @-_*]

API docs for Zoom are located here https://marketplace.zoom.us/docs/api-reference/introduction

Requests can only be made to domains associated by this application.

These params will be URL-encoded and appended to the URL when making the request.

Authentication headers are included automatically

Zapier will apply these optional headers and values to the request in addition to any headers created as part of the authentication mechanism.

Zapier will pass this along raw. If you would like to provide complex JSON, try a "Code by Zapier" step to build the structure and pass it along here. For example, {"foo": "bar"} is perfectly valid.