Recurly

undefined

Detail	Value
Category	Finance
Base URL	https://v3.recurly.com
Authentication	Basic Auth
Endpoints	5
Connector key	recurly

Using Recurly in a workflow

1. Go to Connections and click New Connection.
2. Pick Recurly from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET	Accounts
GET	Subscriptions
GET	Plans
GET	Invoices
GET	Transactions

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET

Accounts

Detail	Value
Operation ID	accounts_0
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Recurly connection from the Connection dropdown.
3. In the Operation dropdown, select accounts_0.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Recurly API reference.

GET

Subscriptions

Detail	Value
Operation ID	subscriptions_1
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Recurly connection from the Connection dropdown.
3. In the Operation dropdown, select subscriptions_1.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Recurly API reference.

GET

Plans

Detail	Value
Operation ID	plans_2
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Recurly connection from the Connection dropdown.
3. In the Operation dropdown, select plans_2.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Recurly API reference.

GET

Invoices

Detail	Value
Operation ID	invoices_3
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Recurly connection from the Connection dropdown.
3. In the Operation dropdown, select invoices_3.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Recurly API reference.

GET

Transactions

Detail	Value
Operation ID	transactions_4
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Recurly connection from the Connection dropdown.
3. In the Operation dropdown, select transactions_4.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Recurly API reference.