> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/analyze/integrated-webhooks/integrated-webhooks-tutorial-videos/integrated-webhooks-mercado-pago-with-sprinthub.md). # Integrated Webhooks: Mercado Pago with SprintHub This integration with Mercado Pago aims to bring the buyer's registration data into SprintHub. In this example, we will bring only the credit card name and email. {% embed url="" %} {% hint style="danger" %} Prerequisite: Have studied and tested the integrated Webhooks tutorials: {% endhint %} ### Integration flowchart.

For a better understanding of this step-by-step guide, watch the video above. \ \
### Step 1:
Register and access Mercado Pago's Developers area:

On the Apps screen, create a new app “Create application”. \
### Step 2: \ In SprintHub, under Custom Fields, create the fields you want to bring from Mercado Pago. In the example in this tutorial, besides Client ID and Merchand Order, I am bringing only the Order ID field.

\ Keep Client ID as the unique identifier. \
### Step 3: Go to Integration Webhooks and create a new Passive webhook. ?

Do the automatic mapping, but then create a new field called ID because what comes in production in real sales is different from what comes in the test submission during mapping. \

**Extra Actions:** Create an extra action called “Send integration webhook”. Do this step only after you create active webhooks 02 and 03 as shown in the video and in the screens below.

Configure the token as below. Watch the video to find out where to get the token. \ \

**Automatic Lead Creation:** Update and automatically create the Lead by mapping these fields. \
### Step 04:
Create an Active Webhook called 02 - MP - Fetch Order ID \

Map as above. This is what we will fetch from this endpoint:
Destination URL: [https://api.mercadopago.com/merchant\_orders/{contactfield=mp\_merchant\_order](https://api.mercadopago.com/merchant_orders/%7Bcontactfield=mp_merchant_order)} \

In the Array configuration, I am only fetching id and status, but you can fetch other data within the payment object. \ \

**Return validation:** In the example, I want to bring only what has status approved. \ \

**Extra Actions:** I am adding the payment ID in the MP - Order ID field. \

I am calling webhook 03, where I will pass the Payment ID to bring the buyer's data. ### Step 05: Create a new active webhook called 03 - MP - Fetch Payment Data with Order ID

Destination URL: [https://api.mercadopago.com/v1/payments/{contactfield=id\_da\_compra](https://api.mercadopago.com/v1/payments/%7Bcontactfield=id_da_compra)} \ \

**Extra Actions:** This call will update the Contact, Name, and Email fields. \
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.sprinthub.com/en/topics/analyze/integrated-webhooks/integrated-webhooks-tutorial-videos/integrated-webhooks-mercado-pago-with-sprinthub.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.