Configure mutation trigger - woudt/bunq2ifttt GitHub Wiki
Introduction
This is a trigger that fires when a mutation is received. You can set many different filters to precisely select which transactions you want to receive.
1. Create new trigger
In IFTTT platform, go to API -> Triggers and click on the New trigger button. You can then enter the following details:
- Name:
bunq mutation(can be changed to anything you like) - Description:
This trigger fires when bunq sends a mutation for a given account.(can be changed to anything you like) - Endpoint: choose API and use
bunq_mutationin the URL. Note: this must match exactly!
See screenshot.
2. Trigger fields
Once the trigger had been created, the first step is to define all trigger fields.
Below are all the possible trigger fields. You can add them all for maximum flexibility, but you can also add a subset.
| Account | [ screenshot ] |
|---|---|
| Label: | Account |
| Description: | Select the account on which to monitor mutations |
| Key name: | account |
| Input type: | Dropdown list |
| Data source for dropdown list: | Retrieve list items for my service |
| Type | [ screenshot ] |
| Label: | Type |
| Description: | Select the type of mutations to filter on |
| Key name: | Type |
| Input type: | Dropdown list |
| Data source for dropdown list: | Retrieve list items for my service |
| Type | [ screenshot ] |
| Label: | Type 2 |
| Description: | Optionally select a second type of mutations to filter on |
| Key name: | Type_2 |
| Input type: | Dropdown list |
| Data source for dropdown list: | Retrieve list items for my service |
| Type | [ screenshot ] |
| Label: | Type 3 |
| Description: | Optionally select a third type of mutations to filter on |
| Key name: | Type_3 |
| Input type: | Dropdown list |
| Data source for dropdown list: | Retrieve list items for my service |
| Type | [ screenshot ] |
| Label: | Type 4 |
| Description: | Optionally select a fourth type of mutations to filter on |
| Key name: | Type_4 |
| Input type: | Dropdown list |
| Data source for dropdown list: | Retrieve list items for my service |
| Amount comparator | [ screenshot ] |
| Label: | Amount comparator |
| Description: | Comparator for the Amount value field |
| Key name: | amount_comparator |
| Input type: | Dropdown list |
| Data source for dropdown list: | Retrieve list items for my service |
| Amount value | [ screenshot ] |
| Label: | Amount account value |
| Description: | Value to compare the mutation amount with |
| Key name: | amount_value |
| Input type: | Text input |
| Amount comparator 2 | [ screenshot ] |
| Label: | Amount comparator 2 |
| Description: | Comparator for the Amount value 2 field |
| Key name: | amount_comparator_2 |
| Input type: | Dropdown list |
| Data source for dropdown list: | Retrieve list items for my service |
| Amount value 2 | [ screenshot ] |
| Label: | Amount value 2 |
| Description: | Second value to compare the mutation amount with |
| Key name: | amount_value_2 |
| Input type: | Text input |
| Balance comparator | [ screenshot ] |
| Label: | Balance comparator |
| Description: | Comparator for the Balance value field |
| Key name: | balance_comparator |
| Input type: | Dropdown list |
| Data source for dropdown list: | Retrieve list items for my service |
| Balance value | [ screenshot ] |
| Label: | Balance account value |
| Description: | Value to compare the balance after mutation with |
| Key name: | balance_value |
| Input type: | Text input |
| Balance comparator 2 | [ screenshot ] |
| Label: | Balance comparator 2 |
| Description: | Comparator for the Balance value 2 field |
| Key name: | balance_comparator_2 |
| Input type: | Dropdown list |
| Data source for dropdown list: | Retrieve list items for my service |
| Balance value 2 | [ screenshot ] |
| Label: | Balance value 2 |
| Description: | Second value to compare the balance after mutation with |
| Key name: | balance_value_2 |
| Input type: | Text input |
| Counterparty account comparator | [ screenshot ] |
| Label: | Counterparty account comparator |
| Description: | Comparator for the Counterparty account value field |
| Key name: | counterparty_account_comparator |
| Input type: | Dropdown list |
| Data source for dropdown list: | Retrieve list items for my service |
| Counterparty account value | [ screenshot ] |
| Label: | Counterparty account value |
| Description: | Value to compare the counterparty IBAN with |
| Key name: | counterparty_account_value |
| Input type: | Text input |
| Counterparty account comparator 2 | [ screenshot ] |
| Label: | Counterparty account comparator 2 |
| Description: | Comparator for the Counterparty account value 2 field |
| Key name: | counterparty_account_comparator_2 |
| Input type: | Dropdown list |
| Data source for dropdown list: | Retrieve list items for my service |
| Counterparty account value 2 | [ screenshot ] |
| Label: | Counterparty account value 2 |
| Description: | Second value to compare the counterparty IBAN with |
| Key name: | counterparty_account_value_2 |
| Input type: | Text input |
| Counterparty name comparator | [ screenshot ] |
| Label: | Counterparty name comparator |
| Description: | Comparator for the Counterparty name value field |
| Key name: | counterparty_name_comparator |
| Input type: | Dropdown list |
| Data source for dropdown list: | Retrieve list items for my service |
| Counterparty name value | [ screenshot ] |
| Label: | Counterparty name value |
| Description: | Value to compare the counterparty name with |
| Key name: | counterparty_name_value |
| Input type: | Text input |
| Counterparty name comparator 2 | [ screenshot ] |
| Label: | Counterparty name comparator 2 |
| Description: | Comparator for the Counterparty name value 2 field |
| Key name: | counterparty_name_comparator_2 |
| Input type: | Dropdown list |
| Data source for dropdown list: | Retrieve list items for my service |
| Counterparty name value 2 | [ screenshot ] |
| Label: | Counterparty name value 2 |
| Description: | Second value to compare the counterparty name with |
| Key name: | counterparty_name_value_2 |
| Input type: | Text input |
| Description comparator | [ screenshot ] |
| Label: | Description comparator |
| Description: | Comparator for the Description value field |
| Key name: | description_comparator |
| Input type: | Dropdown list |
| Data source for dropdown list: | Retrieve list items for my service |
| Description value | [ screenshot ] |
| Label: | Description value |
| Description: | Value to compare the mutation description with |
| Key name: | description_value |
| Input type: | Text input |
| Description comparator 2 | [ screenshot ] |
| Label: | Description comparator 2 |
| Description: | Comparator for the Description value 2 field |
| Key name: | description_comparator_2 |
| Input type: | Dropdown list |
| Data source for dropdown list: | Retrieve list items for my service |
| Description value 2 | [ screenshot ] |
| Label: | Description value 2 |
| Description: | Second value to compare the mutation description with |
| Key name: | description_value_2 |
| Input type: | Text input |
3. Verbiage
It doesn't really matter what you put here. A suggestion is to use:
bunq account {{fields.account.label}} receives a {{fields.type.label}} mutation
4. Ingredients
By default there already is a 'CreatedAt' ingredient.
The following are all possible ingredients. You can add them all (highly suggested), but feel free to leave out ones you do not need.
| Date | [ screenshot ] |
|---|---|
| Name: | Date |
| Slug: | date |
| Note: | The transaction date in YYYY-MM-DD format |
| Type: | String |
| Example: | 2018-12-31 |
| Type | [ screenshot ] |
| Name: | Type |
| Slug: | type |
| Note: | Mutation type |
| Type: | String |
| Example: | IDEAL |
| Amount | [ screenshot ] |
| Name: | Amount |
| Slug: | amount |
| Note: | The amount of the mutation |
| Type: | String |
| Example: | -10.00 |
| Balance | [ screenshot ] |
| Name: | Balance |
| Slug: | balance |
| Note: | The balance after the mutation |
| Type: | String |
| Example: | 175.23 |
| Account | [ screenshot ] |
| Name: | Account |
| Slug: | account |
| Note: | IBAN of the source account (same as selected) |
| Type: | String |
| Example: | NL42BUNQ2013456789 |
| AccountName | [ screenshot ] |
| Name: | AccountName |
| Slug: | account_name |
| Note: | Name/description of the source account |
| Type: | String |
| Example: | Groceries account |
| CounterpartyAccount | [ screenshot ] |
| Name: | CounterpartyAccount |
| Slug: | counterparty_account |
| Note: | IBAN of the counterparty |
| Type: | String |
| Example: | NL42BANK0123456789 |
| CounterpartyName | [ screenshot ] |
| Name: | CounterpartyName |
| Slug: | counterparty_name |
| Note: | Name of the counterparty |
| Type: | String |
| Example: | Acme Inc. |
| Description | [ screenshot ] |
| Name: | Description |
| Slug: | description |
| Note: | Description delivered with the mutation |
| Type: | String |
| Example: | Invoice 12345 |
| PaymentId | [ screenshot ] |
| Name: | PaymentId |
| Slug: | payment_id |
| Note: | Unique payment identifier |
| Type: | String |
| Example: | 123e4567-e89b-12d3-a456-426655440000 |
5. Applet templates
These are completely optional. Here are some suggestions:
Mobile push notifications:
Transferred {{Amount}} from/to {{CounterpartyAccount}}
Short message:
Transferred {{Amount}} from/to {{CounterpartyAccount}}
Long post:
- Post title:
bunq mutation - Post body:
Created: {{CreatedAt}}<br>Type: {{Type}}<br>Account: {{Account}}<br>Amount: {{Amount}}<br>Balance after mutation: {{Balance}}<br>Counterparty account: {{CounterpartyAccount}}<br>Counterparty name: {{CounterpartyName}}<br>Description: {{Description}}
Spreadsheet:
- Spreadsheet name:
bunq_mutations_{{Account}} - Formatted row:
{{Account}}|||{{CreatedAt}}|||{{Date}}|||{{Type}}|||{{Amount}}|||{{Balance}}|||{{CounterpartyAccount}}|||{{CounterpartyName}}|||{{Description}}|||{{PaymentId}}
6. 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 mutation trigger correctly!