Skip to content

Configure change card account action

Edwin Woudt edited this page Dec 4, 2019 · 2 revisions

Introduction

This is an action that changes the account connected to a particular (physical) card.

1. Create new action

In IFTTT platform, go to API -> Actions and click on the New action button. You can then enter the following details:

  • Name: bunq change card account (can be changed to anything you like)
  • Description: This action will change the account connected to a particular (physical) card. (can be changed to anything you like)
  • Verbiage: Leave empty for now
  • Endpoint: bunq_change_card_account Note: this must match exactly!

See screenshot

2. Create action fields

Once the action is created, you need to add the following action fields:

Note that the card and account fields are compulsory, but if you only every change the primary account of a card, the PIN Ordinal field can be left out.

Card [ screenshot ]
Label: Card
Optional helper text: Select the card
Key name: card
Required: yes (This action field is required for Applets to work)
Action field type: Dropdown list / Retrieve list items from my service
PIN Ordinal (optional)
:------------------------ :-------
Label: PIN Ordinal
Optional helper text: Change the account for the primary of secondary PIN?
Key name: pin_ordinal
Required: no (This action field is optional)
Action field type: Dropdown list / Retrieve list items from my service
Account [ screenshot ]
Label: Account
Optional helper text: Select the account
Key name: account
Required: yes (This action field is required for Applets to work)
Action field type: Dropdown list / Retrieve list items from my service

3. Verbiage

Save the page, after which it is possible to add the verbiage using action field ingredients:

change card {{fields.card.label}} to account {{fields.account.label}}

4. Finally

Once you are done, the result should look something like this screenshot

Go to API -> Endpoint tests and click on the 'Begin test' button. In case all results are green: congratulations, you configured the draft payment action correctly!