Chargify
Configuration and usage guide for the Chargify connector in Recurly Engage.
The Chargify integration lets you manage subscriptions and coupons directly from your prompts, using your Chargify billing system to automate user plan changes and coupon applications.
Available on all Recurly Engage subscription plans
Prerequisites
- You must have Company or App Administrator permissions in Recurly Engage.
- You must have a valid Chargify account with API access.
Limitations
- User records in Recurly Engage must include the
chargify_idtrait for action targeting.
Definition
The Chargify connector synchronizes products, coupons, and subscription data from Chargify into Recurly Engage, so you can trigger billing-related actions from within prompts.
Key benefits
Automated billing workflows
Create or cancel subscriptions directly from prompts.
Coupon management
Apply coupon codes in real time as users interact.
Uninterrupted user flow
Keep users in the flow without manual backend steps.
Key details
Required settings
Configure your Chargify connector under Settings > Connectors:
- API Key: Your Chargify API key.
- Domain: Your Chargify site domain (for example,
your-site.chargify.com).
Data integration
- Products and coupons are synchronized on a scheduled basis, so they're available in prompt configurations.
- Chargify ID must be mapped to the user's
chargify_idtrait in Recurly Engage for action execution.
Supported actions
Use these actions within your prompt configurations to perform billing operations:
| Action | Description | User dependencies | Additional instructions |
| Create subscription | Subscribes a user to a specified Chargify product plan | chargify_id | Select the desired plan from the connector dropdown. |
| Cancel subscription | Cancels a user's existing subscription to a product plan | chargify_id | Choose which plan to cancel on the prompt screen. |
| Add coupon code | Applies a coupon code to a user's subscription | chargify_id | Select both the plan and coupon code on the prompt. |
Updated 17 days ago
Did this page help you?