Triggers when a new campaign starts sending.

Triggers when a new contact note is added.

Triggers whenever a contact is added to a list.

Triggers when a new contact is created or an existing contact's details are updated.

Creates a new account.

Creates a new account or updates an existing account.

Creates a new deal.

The contact will be removed from this active automation

Adds a contact to an ActiveCampaign account

Add or remove a tag from a Contact

Creates a new custom object record or update an existing record

Creates a new deal.

Creates or updates a deal task

Start an outbound WhatsApp messaging flow for a phone number.

Creates a custom website or application event.

This is an advanced action which makes a raw HTTP request that includes this integration's authentication.

Finds a contact by email address, ID, or phone.

Finds an existing deal by title or email.

Finds a deal task.

Search for a WhatsApp Template to use.

Make a call to this endpoint when a user adds a product to their shopping cart.

Make a call to this endpoint for any event-based data representing user actions.

Get Custom Attributes for a User

Make a call to this endpoint to subscribe a user to subscriptions. Note that when a user is subscribed programmatically, it must include

Make a call to this endpoint when a user views a product.

Creates or updates a single user record, including associated attributes, subscriptions, and identifiers. If a user with the provided identifiers already exists, their information will be updated; otherwise, a new user will be created. There is a limit of 100 of custom attributes that can be created. If intending to update an existing attribute, the name of the key must match the name of the existing attribute. If an existing attribute does not exist, a new attribute will be created with the given key as the name. Attributes with enumerated values must have a value that matches an existing enum value; new enum values will not be created. Attempting to pass custom attributes as an array or a map such as ["New York City] or {"favorite city": "Boston"} will result in a 400 error.

Triggers when a contact unsubscribes as a result of a campaign email sent to them.

Triggers when a new contact task is created.

Triggers when a new contact is created.

Triggers when an existing contact details are updated.

Triggers when a a Tag is added or removed from a Contact

Updates an account.

Creates a new contact, or updates an existing contact.

Adds an existing contact into any automation.

Creates and sends a new campaign.

Adds new contact note.

Creates or updates a contact task

With a deal ID and a contact ID set the corresponding contact as a secondary on the deal. Optionally set the role. If the Deal has no Primary contact set, this contact will be set as Primary if you DO NOT select a role.

Adds a note to a deal.

Updates an existing deal.

Subscribes a Contact to a List it is not currently associated with, or Unsubscribes a Contact from a list is currently associated with.

Send a Whatsapp approved template to any number

Finds account by name.

Finds a contact task.

Looks for a Deal and if found, returns the User that owns the Deal

Finds a user by email address.

Make a call to this endpoint for any attribute-based data.

You can use the Privacy Request API in order to comply with

Make a call to this endpoint to get recent catalog uploads with their statuses to gain visibility into the ingestion workflow in order of creation. See the POST of this endpoint for details.

Use the Identity API to manage user identifiers. With this API, you can programmatically add a client user identifier or custom identifier(s) to a user. You should only use clientUserId and customIdentifiers to send Attentive your system-assigned unique identifiers (even when testing).

Make a call to this endpoint to unsubscribe a user from a subscription type or channel. If no subscriptions are present in the request, the user is unsubscribed from all subscriptions. If subscriptions are present in the request, the user is unsubscribed from the requested type or channel combination. By default, if a subscription exists, but the user is already unsubscribed, it records the attempt to unsubscribe the subscription again. For TEXT subscriptions, a message is sent to the person indicating that they are unsubscribed.

Make a call to this endpoint when a user generates an order or purchase.

Make a call to this endpoint to list all subscription types and channels a user is subscribed to. You can query for a subscriber using either their phone number or email. One of the query parameters is required in order to look up a subscriber. As an example, you can use this endpoint to check if a subscriber is eligible to receive SMS or email campaigns, and then send them a message based on that eligibility.