Instagram messages, Messenger and lead ads open to every organization once Meta finishes reviewing Marro’s app.
Facebook & Instagram lead ads
1
Log in with Facebook
In Settings → Integrations → Facebook & Instagram lead ads, press Log in with Facebook with the account that runs your Page, and allow what it asks.
2
Choose your Pages
Pick the Pages your ads run from.
3
Check your forms
Each form’s questions are matched to your lead fields. Change a match if needed, then press Done.
Google Ads lead forms
Leads from your Google Ads lead forms (Search, YouTube, Demand Gen and Performance Max) arrive in Marro within seconds. There is no Google sign-in: Google sends each lead to a web address and key that Marro makes for you. You can add several connections, for example one per Google Ads account, brand or agency, each with its own address and key.1
Add a connection
In Settings → Integrations → Google Ads lead forms, press Add connection and give it a name you will recognise, such as “Admissions – Search”.
2
Copy the address and key
Open the connection. Its Connection setup section shows a Webhook URL and a Key. Keep the key private: anyone who has it could send leads to this connection.
3
Paste them into Google Ads
In Google Ads open Assets, edit your lead form, choose Webhook for lead delivery and paste the Webhook URL and Key.
4
Send test data
Press Send test data in Google Ads. A test lead appears under the connection’s Recent leads section within seconds. A test with a phone number becomes a lead named “Google test lead”; delete it when you are done. Then save the form.
5
Check where answers go
When a form’s first lead arrives, open the connection’s Forms and field mapping section. Each question is already matched to a lead field; anything that does not fit is kept in a note on the lead. Change a match if you like. Google sends only campaign numbers, so you can give each campaign a name there.
Google Sheets
Keep a Google Sheet and your leads in step: new rows become leads, and new leads and changes appear as rows. Marro sees only the sheet you choose, never the rest of your Google Drive. Each connection is one Google account and one sheet. Add another connection for another sheet, for example one per team or campaign.1
Connect a sheet
In Settings → Integrations → Google Sheets, press Connect a sheet and sign in with the Google account that owns the sheet.
2
Choose the sheet
Pick an existing sheet with Google’s file picker, or press Create a new sheet and Marro makes one with a header row. Marro adds a Marro ID column at the end; it links each row to its lead, so you can sort the sheet freely. Do not delete or edit that column.
3
Check the columns
In the Column mapping section each column is matched to a lead field by its name. Change a match, or set a column to Not shared and Marro never reads or changes it.
4
Choose the direction and the leads
In the Sync settings section choose Both ways, Sheet to CRM only or CRM to sheet only, and share all leads or just one saved lead list. Sync direction, lead list and column mapping save together. Press Save and start syncing; later changes use Save sync settings and mapping.
SMS (MSG91)
You need an MSG91 account with your sender ID and templates registered on the DLT portal.- In Settings → Integrations → MSG91 (SMS), enter your Auth key, Sender ID and DLT entity ID.
- On the same page, add your SMS templates with their MSG91 and DLT template IDs, and choose the lead detail that fills each blank.
- Send a test SMS to your own phone.
- Turn on delivery reports in MSG91 with the callback URL and header shown on the page.
Phone calls (MCube)
Connect MCube to log the calls your team takes on your MCube numbers. On the MCube integration page, copy the Call events URL and ask MCube to set it as the push URL for incoming call events (On Call and On Hangup) on your account.- Each call is written on the caller’s lead, found by phone number, or a new lead (source Phone call) assigned by your rules.
- An answered call is logged under the executive who took it, with the talk time and recording, and marks the lead contacted. Each executive’s phone number in Marro must match the one MCube rings.
- Every call also appears in Calls, for the leads each person can open, shown as Bridge call · MCube. Calls from other connected calling services such as Exotel or Tata Smartflo appear there the same way.
- A missed call shows as Missed call, and the lead’s owner gets a missed-call alert by email, WhatsApp and the app. Automations can start on missed calls only, for example to add a follow-up.
- When you start a call from a lead through a connected calling service, Marro follows it until it ends. If the service does not report back, Marro asks the service itself (Exotel and Tata Smartflo can be asked) and closes a call that is still unreported after 45 minutes, so you can call again; a report that arrives later still updates it. If the service could not confirm the call started, it shows as Not confirmed: check your phone before calling again. Recordings are copied into Marro, so they stay playable on the lead even if the service’s link expires.
Zapier, Make, Pabbly Connect, n8n and your own webhook
Marro sends events to your workflow’s webhook as they happen. For any other system, choose Custom webhook and enter your ownhttps address. To change Marro from a workflow, call the API with an API key.
1
Paste the workflow's webhook URL
Create a webhook trigger in your workflow tool, copy its URL, and paste it into the service’s page in Settings → Integrations.
2
Choose the events
Anything that can start an automation: a lead added, changed, moved or given a new owner; calls, notes and follow-ups; messages on every channel; web forms; quotes sent, opened, accepted, declined or expired; invoices sent, paid or overdue; payments; appointments; opportunities won or lost; and records of your custom objects added, changed, moved to another stage or deleted. Search the list to find one.
3
Send test event
Send test event posts a made-up lead with every field, so your workflow learns the field names.
POST with a JSON body of id, event, occurredAt, test (on test events only), organization, lead and change. Check the X-CRM-Signature header: sha256= followed by the hex HMAC-SHA256 of the raw body, keyed with the Signing secret shown on the page. X-CRM-Event names the event and X-CRM-Delivery identifies the delivery.
An event that gets no answer, a 429 or a 5xx is tried again after 1 minute, 5 minutes, 30 minutes, 2 hours and 8 hours, then dropped. Every try has the same X-CRM-Delivery, so your workflow can ignore one it has already had.