Example
Let's say you have an existing workflow that, when triggered through webhook, creates a card in Trello, and sends the card details through email.
Let's create a dynamic, or parameterized account for Trello and Gmail.
- Retrieve service access token and create object.Using your account's OAuth server, create an access token for the service \(in this case, Trello\) and insert it in the access\_token field of the following object. This is the standard object to be used for all service actions:
[ { "auth" : { "access_token" : "9276fb05d973105df631d29894a8b49af8564b85951d121d0ca584a29761d89c" }, "actions" : [ "a0" ] } ]Here, a0 refers to the Id of the action you want to create a parameterized account for. You can find this Id at the lower-left corner of the action configuration window.
-
Next, retrieve an access token for the Gmail service and add it to the object for Gmail service. Add this object below the Trello object. So, it becomes:
[ { "auth" : { "access_token" : "9276fb05d973105df631d29894a8b49af8564b85951d121d0ca584a29761d89c" }, "actions" : [ "a0" ] }, { "auth" : { "access_token" : "ya94.GltcBIa387LWmFugL3Zi9m23yslgx4xkaIzeUR6ZeHkYD0ZfcBQdLHi2A" }, "actions" : [ "a1" ] } ] -
Encode object. Once you have created the object, encode it with base64 encoding. You can use this online service to encode the object.

-
Append encoded object to webhook URL.
Once you have encoded the object, you can append it to the webhook URL of the workflow you wish to execute. Add ?authorizations= to your webhook URL, followed by your encoded object.
For example, if https://runflow.built.io/run/8... is the webhook URL of the workflow, add ?authorizations= followed by the encoded data. Your webhook URL will look something like this: https://runflow.built.io/run/8...?authorizations=IFsgDQogICAgICAgeyANCiAgICAgICAgICJ0b2tlbiIgO…
- Execute the webhook URL. Now, when you execute the above webhook URL, it will call the workflow and replace the existing accounts with the parameterized accounts.