POST: your backend, a Zapier, n8n or Make flow, or a tool with its own notice.
Brein reads the first real notice, suggests what each field is and you confirm. Everything happens in Settings → Integrations. Only the workspace owner or an admin can connect and confirm the mapping.
1
Create the Integration
In Settings → Integrations, choose Connect → Other tool, give it a name and, if you want each notice to open an Opportunity, pick the Pipeline and stage.
2
Copy the secret address
Brein gives you an address shaped like this:The token is the Integration’s password. It is shown only once. Brein stores only a fingerprint of the token, so it cannot show it again. Keep it like any secret.
3
Send the first real notice
Paste the address into your tool and trigger a real notice: a signup, a payment, a response. Or try Brein answers
curl:202 with the Arrival id and the status unmapped: there is no mapping yet, so the notice is stored as the example and no Contact is created.4
Review what Brein detected
On the Integration’s page you see the example with every field and what Brein suggests for it. Detection uses rules, no AI:
- The email by its shape (
something@domain.mx) and the LinkedIn by its address. - The phone if it starts with
+and has 7 to 15 digits, or if the field name says so (telefono,phone,celular,whatsapp). - The name, company, role and website by the field name, in Spanish or English (
nombre,name,empresa,company,cargo,role,sitio,website). A first name and a last name in the same block are joined in that order. - The notice id (
id,event_id,uuid…) and the event type (type,event,topic…): they do not go to the Contact. They prevent duplicates and tell notices apart. - Fields of whoever organizes or administers, or of a product, plan or form, are not taken as the person.
5
Choose the customer's email
If the notice has more than one email, or more than one phone, Brein flags it and you choose which one is the customer’s. The others are ignored.
6
Decide where each field goes and confirm
Each field can go to:
The mapping needs at least one email, phone or LinkedIn field. Once confirmed, the mapping is fixed and has a version number. Each change raises the version.
Batch notices
Some tools send several people in one notice, for example{ "items": [ ... ] } or a list at the top level. Brein recognizes lists named data, events, items, records, results, entries or rows. Each element of the list becomes its own Arrival, with its own result. An element that fails does not stop the others. The response carries a list with the result of each one.
New fields
The mapping is fixed. If one day the notice carries a field that was not in the example, Brein does not store it: it shows it as a new field, undecided. Choose where it goes, or ignore it, and it leaves the list. Until then, that field does not reach the Contact. Up to 200 new fields are kept per Integration.Change the mapping and reprocess
You can fix the mapping any time on the Integration’s page. Changing it does not touch what was already accepted. For Arrivals that ended up no person or not understood:- Fix the mapping.
- Choose Reprocess, on one Arrival or on all of the Integration’s.
Rotate the address
If the address leaked, or someone who had it should no longer have it, use Rotate. Brein creates a new address, shown only once. The old one stops working immediately: update your tool before it sends the next notice, or it will arrive as rejected.Limits
If you are a developer and want to sign your requests, the signed contract is in Send events to Brein.
What happens to each Arrival, how a person is recognized and what is stored: Integrations.