List Recurly Invoices: Recurly action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Account ID or Code account_id	string	Optional	Filter invoices to a single account (use code-<your_code> for code lookup)
State state	options	Optional	Invoice state filter
Limit limit	number	Optional	Max invoices to return

Sample request

{
  "account_id": "{{trigger.account_id}}",
  "state": "{{trigger.state}}",
  "limit": "{{trigger.limit}}"
}

Returns

{
  "data": [
    {
      "id": "inv_123",
      "state": "paid",
      "total": 49,
      "number": "1001",
      "account": {
        "id": "acct_abc123",
        "code": "user_123"
      },
      "currency": "USD",
      "created_at": "2026-04-15T10:00:00Z"
    }
  ],
  "has_more": false
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about List Recurly Invoices.

What does the List Recurly Invoices action do in Recurly?

Paginated invoices with filters. For accounts-receivable workflows and for sync to accounting systems.

What inputs does List Recurly Invoices require?

List Recurly Invoices has no required inputs. Sensible defaults are applied if you leave fields blank.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Recurly returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List Recurly Invoices support batch operations?

Yes. Run List Recurly Invoices inside a Loop node to process arrays. Tiny Command handles Recurly's rate limits automatically so you don't have to throttle manually.

More actions