Connector actions let your in-app prompts do real work in the rest of your stack. When a user interacts with a prompt, Recurly Engage can trigger the right operation in your billing, marketing, support, or analytics tools automatically.

Available on all Recurly Engage plans

Additional cost

Adobe and Salesforce integrations can be purchased for an add-on fee. Contact [email protected] or your Recurly account manager for pricing details.

1Definition 2Key benefits 3Key details

Prerequisites

You must have Company or App Administrator permissions in Engage.
Relevant third-party accounts and API credentials must be provisioned before you configure connectors.

Definition

Connector actions are predefined integrations that let you execute operations in external systems when users interact with your in-app prompts, such as clicking a call to action (CTA). You configure these actions in the Engage console, and they're invoked automatically at runtime.

Key benefits

Automate workflows Trigger downstream processes like billing updates or customer relationship management (CRM) entries without manual intervention.

Unified interface Manage all third-party integrations from a single console.

Flexible triggers Actions can run on accept, secondary accept, decline, dismiss, or timeout events.

Key details

Connector actions require that certain user attributes (for example, account IDs, email addresses, and device tokens) be synced into Engage beforehand. See each connector's documentation for specific data dependencies.

Connector categories and links

Billing

The In-app purchases connector covers Apple, Google, Amazon, and Roku.

CRM & marketing

Salesforce Marketing Cloud

Analytics & events

Configuring a connector

Open Actions settings

Navigate to Settings > Actions in the Engage console.

Select a connector

Select the connector you want from the list.

Enter your credentials

Enter the required API credentials and configuration fields.

Activate the connector

Toggle Active and click Save.

After activation, connector actions appear in each prompt’s Actions configuration panel, where you can assign them to specific user interaction events.