-
Notifications
You must be signed in to change notification settings - Fork 8
Configure oauth expires trigger
This is a trigger that fires when the OAuth connection expires in a given number of hours. This can be very useful to ensure you renew your OAuth connection in time before your triggers and actions stop working, e.g. by sending you a notification or email at certain intervals. Please note that OAuth connections expire after 90 days, so you need to renew the connection before that.
In IFTTT platform, go to API -> Triggers and click on the New trigger button. You can then enter the following details:
-
Name:
bunq oauth expires
(can be changed to anything you like) -
Description:
This trigger fires a number of given hours before the OAuth connection expires after 90 days.
(can be changed to anything you like) -
Endpoint: choose API and use
bunq_oauth_expires
in the URL. Note: this must match exactly!
Once the trigger had been created, the first step is to define all trigger fields. There is only one trigger field for this trigger.
Hours | |
---|---|
Label: | Hours |
Description: | Number of hours before expiry |
Key name: | hours |
Input type: | Text input |
It doesn't really matter what you put here. A suggestion is to use:
the bunq OAuth connection expires in {{fields.hours}} hours
By default there already is a 'CreatedAt' ingredient.
There is one additional ingredient, which you can add (highly suggested), but feel free to leave it out if you don't need it.
ExpiresAt | |
---|---|
Name: | ExpiresAt |
Slug: | expires_at |
Note: | Date and time the OAuth connection expires. |
Type: | Date with time (ISO8601) |
Once you are done, go to API -> Endpoint tests and click on the 'Begin test' button. In case all results are green: congratulations, you configured the oauth expires trigger correctly!