Short answer: Drop the "Recurly → Create Recurly Account" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Account Code code | string | Required | Your unique identifier for this customer (often your internal user ID) |
Email email | string | Optional | Primary email for billing |
First Name first_name | string | Optional | — |
Last Name last_name | string | Optional | — |
Company company | string | Optional | — |
{"code": "user_123","email": "user@example.com","first_name": "{{trigger.first_name}}","last_name": "{{trigger.last_name}}","company": "{{trigger.company}}"}
{"id": "acct_abc123","code": "user_123","email": "user@example.com","state": "active","last_name": "Doe","created_at": "2026-04-15T10:00:00Z","first_name": "John"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.