Manage the creation and deletion of Revolut draft payments from Airtable
Manage the creation and deletion of Revolut draft payments from Airtable
Apps used in template
About
Watch the records of an Airtable base and based on a certain trigger field create or delete Revolut draft payments.
The setup of the template assumes your Airtable table includes the following fields: Name of the recipient of the payment (First name and Last name if it's an individual), Recipient type (INDIVIDUAL or COMPANY), Status (Pay or Cancel), Amount, Payment ID and payment details. There also needs to be a field of type 'Created time' or 'Last modified time' (both populated automatically) for Make to register new or updated records.
To see which details are required to create a Revolut draft payment depending on the country, click here. For example, if you're creating a payment to the United Kingdom, your Airtable table needs to include an Account Number and a Sort Code; for payment to Germany, it's IBAN and BIC.
Trusted by thousands of fast-scaling organizations around the globe
Similar templates for inspiration
Looking to get more out of your apps? With Make, you can visually integrate any app into any workflow to save time and resources - no coding required. Try any of these templates in just a few clicks.
Create your own workflow
Create custom workflows by choosing triggers, actions, and searches. A trigger is an event that launches the workflow, an action is the event.
Combines multiple bundles into a single array. This is the opposite of an Iterator.
Сreates multiple records.
Deletes multiple records.
Updates multiple existing records.
Upserts multiple records.
Creates a draft payment.
Creates a new record in Airtable.
Deletes a draft payment by its ID.
Deletes a draft payment transfer.
FAQ
Start by registering for Make. As a new Make user, you’ll automatically be assigned a free account. Once your account is set up, you can start creating your first scenarios. We recommend starting with our step-by-step video tutorial.
A scenario represents a workflow or a project of your own creation, and it is made up of a series of modules that automate apps and services. Creating a scenario allows you to transfer and transform data between apps and services via these modules to automate anything and improve the way you work.
Modules are the main building blocks of automation in Make. Modules represent actions that Make performs with an app, like creating, updating, or deleting data.
Mapping links the modules in your scenario. When you map an item, you connect the data retrieved by one module to another module to perform the desired action. For example, you can map email addresses and subject lines to create a spreadsheet using this data.
How it works
Traditional no-code iPaaS platforms are linear and non-intuitive. Make allows you to visually create, build, and automate without limits.










