Get Mercury Transaction logo

Catalog action Integrations mercury

Fetch a single Mercury transaction by account ID and transaction ID. Returns the amount, status ('pending', 'sent', 'cancelled', 'failed'), counterparty, memo, timestamps, and failure reason if any. Ideal for: checking whether a payment cleared, payment status polling after a payout, reconciling invoices against bank activity.

At a Glance

FieldValue
Action IDmercury-get-transaction
CategoryIntegrations
Connectormercury
Requires gasNo
Funds movementNone declared
Tagsmercury, banking, fiat, transactions, status, read

Payload Schema

FieldTypeRequiredDescription
accountIdstringYesMercury account ID the transaction belongs to (from mercury-list-accounts)
transactionIdstringYesMercury transaction ID to look up
apiKeystringNoMercury API token. Normally injected automatically by the 'mercury' connector — only set this to override the connector's token.

Result Schema

FieldTypeRequiredDescription
idstringYesMercury transaction ID
amountnumber | nullNoAmount in USD — negative for outgoing payments, positive for incoming
statusstringYesTransaction status: 'pending', 'sent', 'cancelled', or 'failed'
kindstring | nullNoTransaction kind (e.g. 'externalTransfer')
counterpartyIdstring | nullNoCounterparty (recipient) ID
counterpartyNamestring | nullNoCounterparty name
notestring | nullNoInternal note on the transaction
externalMemostring | nullNoExternal memo visible to the recipient
createdAtstring | nullNoISO timestamp the transaction was created
postedAtstring | nullNoISO timestamp the transaction posted, null while pending
estimatedDeliveryDatestring | nullNoEstimated delivery date
failedAtstring | nullNoISO timestamp the transaction failed, null unless failed
reasonForFailurestring | nullNoFailure reason, null unless failed
dashboardLinkstring | nullNoLink to the transaction in the Mercury dashboard

Examples

json
{ "type": "mercury-get-transaction", "payload": { "accountId": "example-accountId", "transactionId": "example-transactionId" }, "children": [], "connector": { "type": "mercury", "id": "conn_mercury" }}

Payload fields can use workflow expressions such as {{$trigger.body.amount}}, {{$nodes.fetch.result.price}}, and {{$props.asset}} when the value should come from a trigger, prior node, or reusable workflow prop.