Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Recurly

Manage subscriptions, billing accounts, and recurring revenue with Recurly.

CategoryCommerce
Authenticationcustom
Version0.1.0
Published scopes0 published scopes
Last updatedSeptember 23, 2026

Overview

Connect Recurly with Flows360

Manage subscriptions, billing accounts, and recurring revenue with Recurly.

Use the Recurly connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 5 actions and no declared triggers.

Available actions

  • Create Account
  • Create Subscription
  • Get Account
  • List Subscriptions
  • Custom API Call

Available triggers

  • No triggers are declared in this pinned package.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Recurly
  • Package: @activepieces/piece-recurly@0.1.0
  • Exact artifact digest: sha256:ea04e3ff18847a14d7ec9d87fb2616baeb39c1ff874b0f2787798773e5822ee8
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Account (create_account), Create a billing account in Recurly. Classification: read.
  • Create Subscription (create_subscription), Start a new subscription for an existing Recurly account. Classification: read.
  • Get Account (get_account), Retrieve details for a billing account in Recurly. Classification: read.
  • List Subscriptions (list_subscriptions), Browse subscriptions in Recurly, with an option to filter by account and state. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects5
Supported actions5
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Account Yes No Create a billing account in Recurly.
Create Subscription Yes No Start a new subscription for an existing Recurly account.
Get Account Yes No Retrieve details for a billing account in Recurly.
List Subscriptions Yes No Browse subscriptions in Recurly, with an option to filter by account and state.
Custom API Call Yes No Make a custom API call to a specific endpoint

Supported actions

Create Account · Read

Create a billing account in Recurly.

create_account · Risk: low · Retry: safe

Inputs

  • code · string · Required, A unique account code for this customer, for example acme-123.
  • email · string · Required, The primary email address for the billing account.
  • firstName · string · Optional, The customeru2019s first name.
  • lastName · string · Optional, The customeru2019s last name.
  • company · string · Optional, The company name for this billing account.
Create Subscription · Read

Start a new subscription for an existing Recurly account.

create_subscription · Risk: low · Retry: safe

Inputs

  • accountCode · string · Required, Select the account that should own the subscription.
  • planCode · string · Required, Select the plan for the new subscription.
  • currency · string · Required, The 3-letter ISO currency code to bill in, for example USD.
  • quantity · number · Optional, The subscription quantity. Leave at 1 for standard subscriptions.
Get Account · Read

Retrieve details for a billing account in Recurly.

get_account · Risk: low · Retry: safe

Inputs

  • accountCode · string · Required, Select the account you want to retrieve.
List Subscriptions · Read

Browse subscriptions in Recurly, with an option to filter by account and state.

list_subscriptions · Risk: low · Retry: safe

Inputs

  • accountCode · string · Optional, Optionally select an account to list only that accountu2019s subscriptions.
  • state · string · Optional, Filter subscriptions by state.
  • limit · number · Optional, The maximum number of subscriptions to return.
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Setup

Setup

  1. Add the Recurly connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-recurly@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 5 actions and 0 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Recurly connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-recurly@0.1.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com