...
This process tool plugin allows you to send ADA assets from one account to another on the Cardano blockchain, with option to also embed form data into the transaction metadata according to the CIP-20 standard.
| Note | ||
|---|---|---|
| ||
|
...
| Name | Description |
|---|---|
| Network Type | Select the network to perform transactions on:
"Mainnet" uses real-world currency(s)assets with actual monetary value. Please use "Testnet" for testing purposes. |
| Backend Service | Select the backend service you wish to use to execute your blockchain queries/transactions with:
|
| Blockfrost Project Key | This property will only appear when Backend Service is Blockfrost. The library used in this plugin integrates with Cardano node via Blockfrost backend APIs. Go to blockfrost.io and sign up for an account. There is a free account option. Paste in your generated mainnet/testnet project API key. See blockfrost.io. |
| GraphQL Endpoint URL | This property will only appear when Backend Service is Custom GraphQL API. Paste in the GraphQL endpoint URL of your choice. |
Transaction Details
| Name | Description | |||||
|---|---|---|---|---|---|---|
| Form | Select a form to retrieve transaction data from. All fields from the selected form will be made available for field mapping in the sections below. | |||||
| Asset Configuration | ||||||
| Payment Type | Select the transfer type to perform:
| |||||
| Policy ID | This property will only appear when Payment Type is Native Token or NFT. The policy ID that minted the token. Can use a Hash Variable or simply hardcoded. | |||||
| Asset Name | This property will only appear when Payment Type is Native Token or NFT. The asset name of the token, e.g.: MyTestToken, My-First-NFT. Typically a Hash Variable is used here. | |||||
| Payment Configuration | ||||||
| Sender Address | Address to send funds assets from. Hash Variable is also accepted. | |||||
| Sender Account Mnemonic Phrase | This is the sender's account secret key required in order to perform actions with the sender's account. Only accepts Hash Variable that points to the sender's encrypted stored mnemonic phrase.
| |||||
| Receiver Address | Address to send funds to. Hash Variable is also accepted. | |||||
| Amount To Send (ADA) | Amount of ADA coin(s) to send. Amount can only contain max 6 decimal places. Hash Variable is also accepted. | |||||
| Enable Transaction Metadata | If enabled, additional configurations will be shown to allow embedding form data into the transaction metadata. | |||||
| Form | Only available if Enable Transaction Metadata property is checked. Select a form to retrieve form data. | |||||
| Enable Multiple Receivers | This property will only appear when Payment Type is ADA or Native Token. When this option is checked, you can pull multiple rows of data from a datalist to send assets to multiple receivers with their respective amounts. With this feature, all the receivers are compiled into a single transaction and executed atomically. Binder To Retrieve Receivers property will appear for you to select a datalist binder and then configure the datalist binder accordingly. After then, the Binder Column Mapping (Multiple Receivers Mode) configuration tab will be available for you to map columns accordingly. | |||||
| Binder To Retrieve Receivers | This property will only appear when Enable Multiple Receivers is checked. Select a datalist binder and configure the selected binder accordingly in subsequent configuration tab(s). | |||||
| Receiver Address | This property will only appear when Enable Multiple Receivers is not checked. Address to send assets to. | |||||
| Amount To Send | This property will only appear when Enable Multiple Receivers is not checked. Amount of tokens to send. Amount can only contain max 6 decimal places. This rule applies for both ADA and native tokens. | |||||
| Additional Metadata | ||||||
| Metadata | Metadata | Only available if Enable Transaction Metadata property is checked. Fields available here depends on the Form selected. Select the field(s) you wish to embed into the transaction metadata. Written transaction metadata follows the CIP-20 standard. To learn more about transaction metadata, see https://developers.cardano.org/docs/transaction-metadata/.
| ||||
Binder Column Mapping (Multiple Receivers Mode)
This configuration tab will only appear when Enable Multiple Receivers property is checked.
At Binder To Retrieve Receivers property, select a datalist binder and configure the selected binder accordingly in subsequent configuration tab(s).
| Name | Description |
|---|---|
| Receiver Address | Upon configuring a datalist binder, select the respective column to represent the receiver addresses. |
| Amount | Upon configuring a datalist binder, select the respective column to represent the amount of assets to send to the respective receivers. |
Store Response To Workflow Variable
| Name | Description |
|---|---|
| Is Transaction Successful | To indicate if this transaction has executed successfully. Returns true if successful, otherwise it returns false. You can use this value in your process to route your business logic and fully customize the user experience flow. |
| Is Transaction Validated | To indicate if this transaction has been successfully validated. This value will typically start with a false value. Only after the transaction has been confirmed/validated on the blockchain, only then this value will automatically be changed to true. |
| Transaction ID | To store the transaction ID of the transaction performed. |
| Transaction Explorer URL | To store an auto-generated URL to see transaction details on the official Cardano blockchain explorer. Do note that explorers typically has a short delay to sync to the latest blockchain state in order to reflect your transactions. |