Skip to main content

Make Waves ’26 Step into AI’s glass box. Prague, 19–20 Oct.

Register now (opens in a new tab)
Notifications for Mercado Pago
Airtable

Connect Notifications for Mercado Pago and Airtable

Explore ready-made Notifications for Mercado Pago and Airtable templates and start automating in minutes.

Get started free

Create a custom workflow

Integrate Notifications for Mercado Pago with Airtable and automate the work that moves between them — no code required.

Create a custom workflow

Every automation starts with a trigger and an action. Select one from each app to generate a workflow tailored to your needs.

Notifications for Mercado Pago
Trigger: [DO NOT USE] Watch Authorized Recurrent Payments
Airtable
Action: Select an action
1. Select a trigger

  • Triggers when a new authorized recurrent payment notification is received in Mercado Pago.

  • Triggers when a new payment notification is received in Mercado Pago. Note: payer's email address is included in accredited payments only

  • Triggers when a new subscription notification is received in Mercado Pago. Note: These notifications do not include the payer's email address.

  • Triggers when a new accredited payment notification is received in Mercado Pago

  • Triggers when a new authorized subscription notification is received in Mercado Pago. This trigger does not activate if the subscription includes a free trial period

  • Triggers when a new cancelled subscription notification is received in Mercado Pago.

2. Select an action

  • Deletes multiple records.

  • Creates a new base.

  • Creates a new comment.

  • Creates a new field in an existing table.

  • Creates a new record in Airtable.

  • Creates a record with mapped fields.

  • Creates a new table.

  • Deletes an existing comment. This action cannot be undone.

  • Deletes a record by its ID.

  • Retrieves a single record by its ID.

  • Returns the base schema.

  • Performs an arbitrary authorized API call.

  • Updates an existing comment.

  • Updates the name and/or description of a field.

  • Updates a record by its ID.

  • Updates a record with mapped fields.

  • Updates the name, description, and/or date dependency settings of a table.

  • Uploads an attachment into an attachment field. Only allows files up to 5 MB.

  • Creates new or updates an existing record.

Select a trigger and an action

Create workflow (opens in a new tab)

Triggers and actions

Explore what you can automate between Notifications for Mercado Pago and Airtable.

[DO NOT USE] Watch Authorized Recurrent Payments
Triggers when a new authorized recurrent payment notification is received in Mercado Pago.
Trigger
[DO NOT USE] Watch Payments
Triggers when a new payment notification is received in Mercado Pago. Note: payer's email address is included in accredited payments only
Trigger
[DO NOT USE] Watch Subscriptions
Triggers when a new subscription notification is received in Mercado Pago. Note: These notifications do not include the payer's email address.
Trigger
Bulk create records (advanced)
Сreates multiple records.
Search
Bulk delete records (advanced)
Deletes multiple records.
Action
Bulk update records (advanced)
Updates multiple existing records.
Search
Bulk upsert records (advanced)
Upserts multiple records.
Search
Create a base
Creates a new base.
Action
Create a comment
Creates a new comment.
Action
Load more

Support

FAQs

Everything you need to know about Make. Can't find the answer you're looking for? Please chat to our team.

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.