List Order Transactions

shopify.list_transactions
ActionBusiness appsconnection required

Calls the Shopify API with the connection's credentials.

List the payment transactions recorded against one Shopify order.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
Shopify
Secret shape
the Shopify Admin API access token
Config it needs
shop
Resolved by
config.connection_id, else node.connection_id

Configuration

4 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
order_id
Numeric id of the order to act on.
stringYes——450789469
since_id
Return only records with an id greater than this one — a cheap way to poll for what is new.
stringNo———
in_shop_currency
Return amounts converted into the store's currency instead of the currency the customer paid in.
booleanNo———
fields
Comma-separated list of fields to return instead of the whole resource.
stringNo——id,email,created_at

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "fields": "id,email,created_at",
  "order_id": "450789469"
}

Output

One shape.

result

FieldTypeExample
transactions
The transactions on this page, exactly as Shopify returned them.
array—
count
How many transactions are on this page.
number—
page_info
Cursor for the next page, or empty when this was the last page.
string—
has_more
True when another page exists.
boolean—
{
  "count": 0,
  "has_more": false,
  "page_info": "",
  "transactions": []
}

Notes

  • The store and the API version come from the connection: 'shop' (your-store.myshopify.com) and an optional 'api_version' that defaults to 2026-07. Auth is the Admin API access token, sent as X-Shopify-Access-Token.
  • Lists page on an opaque cursor from Shopify's Link header, not on page numbers. Pass the 'page_info' a call returns back into the next call while 'has_more' is true; a request carrying page_info may only carry 'limit' and 'fields', so every other filter is ignored once you are paging.
  • Shopify rate-limits with a leaky bucket (X-Shopify-Shop-Api-Call-Limit). A 429 fails the step with the bucket state and the Retry-After seconds in the message: put a control.delay in front of the node or lower 'limit'.
  • Each write node also accepts the raw resource object for fields it does not model; that object is merged last and wins on a conflict.
  • Transactions are the authorisations, captures, refunds and voids behind an order's financial status — not the order's totals.

See List Order Transactions run in a workflow.

In a technical demo we add the Shopify connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.