Skip to main content

Make Waves ’26 Step into AI’s glass box. Prague, 19–20 Oct.

Register now (opens in a new tab)
Attentive
WordPress

Connect Attentive and WordPress

Explore ready-made Attentive and WordPress templates and start automating in minutes.

Get started free

Create a custom workflow

Integrate Attentive with WordPress and automate the work that moves between them — no code required.

Create a custom workflow

Every automation starts with a trigger and an action. Select one from each app to generate a workflow tailored to your needs.

Attentive
Trigger: Watch Custom Attribute Set
WordPress
Action: Select an action
1. Select a trigger

  • Triggers when a custom attribute is set.

  • Triggers when a link is clicked in an email message.

  • Triggers when an email is opened.

  • Triggers when an email message is sent.

  • Triggers when a user opts in to an email subscription.

  • Triggers when a user opts out of an email subscription.

  • Triggers when a user replies to an SMS message.

  • Triggers when a link is clicked in an SMS message.

  • Triggers when an SMS is sent.

  • Triggers when a user opts in to an SMS subscription.

  • Triggers when a user opts out of an SMS subscription.

2. Select an action

  • Creates a category.

  • Creates a comment.

  • Creates a media item.

  • Creates a post.

  • Creates a tag.

  • Creates a user.

  • Deletes a category specified by its ID.

  • Deletes a comment specified by its ID.

  • Deletes a media item specified by its ID.

  • Deletes a post specified by its ID.

  • Deletes a tag specified by its ID.

  • Deletes a user specified by its ID.

  • Returns info about a category specified by its ID.

  • Returns info about a comment specified by its ID.

  • Returns info about a media item specified by its ID.

  • Returns info about a post specified by its ID.

  • Returns info about a tag specified by its ID.

  • Returns info about a user specified by its ID.

  • Performs an arbitrary authorized API call.

  • Updates a category specified by its ID.

  • Updates a comment specified by its ID.

  • Updates a media item specified by its ID.

  • Updates a post specified by its ID.

  • Updates a tag specified by its ID.

  • Updates a user specified by its ID.

Select a trigger and an action

Create workflow (opens in a new tab)

Triggers and actions

Explore what you can automate between Attentive and WordPress.

Add a Client User Identifier or Custom Identifier(s) to a User
Add a client user identifier or custom identifier(s) to a user.
Action
Add a Custom Attributes
Add any attribute-based data to a user.
Action
Add a Custom Event
Send user actions to use in the Attentive Segment Builder and Journey Builder for both email and text messages.
Action
Add a Deletion Request
Creates a new privacy deletion request. This will be done within thirty days, provided the call was successful.
Action
Add Offer Codes
Add discount codes to an existing offer.
Action
Add to Cart
A user adds a product to their shopping cart.
Action
Create a Category
Creates a category.
Action
Create a Comment
Creates a comment.
Action
Create a Media Item
Creates a media item.
Action
Load more

Support

FAQs

Everything you need to know about Make. Can't find the answer you're looking for? Please chat to our team.

Start by registering for Make. As a new Make user, you’ll automatically be assigned a free account. Once your account is set up, you can start creating your first scenarios. We recommend starting with our step-by-step video tutorial.

A scenario represents a workflow or a project of your own creation, and it is made up of a series of modules that automate apps and services. Creating a scenario allows you to transfer and transform data between apps and services via these modules to automate anything and improve the way you work.

Modules are the main building blocks of automation in Make. Modules represent actions that Make performs with an app, like creating, updating, or deleting data.

Mapping links the modules in your scenario. When you map an item, you connect the data retrieved by one module to another module to perform the desired action. For example, you can map email addresses and subject lines to create a spreadsheet using this data.