meetergomeetergo Help

LinkedIn lead forms and event registrations to meetergo

Send every LinkedIn Lead Gen Form response and LinkedIn event registration to meetergo as a contact, with Zapier or Make and the contact intake URL. Field mapping, tags, consent and how to start a sequence from the tag.

Updated on October 22, 2026

When someone fills in a LinkedIn Lead Gen Form, on an ad, your company page or a LinkedIn event, you can have that person land in meetergo as a contact a few seconds later. A tag on the contact then starts your email sequence, so reminders go out without anyone copying data by hand.

LinkedIn only hands lead form data to approved partner apps. meetergo is not one of them yet, so the lead travels through Zapier or Make into your contact intake URL.

1. Create your contact intake URL

  1. Open Integrations & Apps and find the Contact intake URL tile under Automation.
  2. Click Connect, then Create URL.
  3. Click Copy. Keep the URL private: anyone who has it can create contacts in your account.

2a. Connect with Zapier

  1. In Zapier, create a Zap.
  2. Trigger: choose the app LinkedIn Ads and the event New Lead Gen Form Response (Organic Content). This covers forms on your company page, product pages and LinkedIn events. For forms in paid ads, choose New Lead Gen Form Response (Sponsored content) instead.
  3. Connect the LinkedIn account that is an admin of the company page, then pick the organization and the form.
  4. Action: choose Webhooks by Zapier and the event POST.
  5. Paste your contact intake URL into URL. Set Payload Type to json.
  6. Under Data, add one row per field from the table below and map the LinkedIn value on the right.
  7. Test the step and turn the Zap on.

2b. Connect with Make

  1. In Make, create a scenario.
  2. Trigger: add LinkedIn Lead Gen Forms → Watch Form Responses and select your form.
  3. Action: add HTTP → Make a request.
  4. Set URL to your contact intake URL, Method to POST, Body type to Raw and Content type to JSON (application/json).
  5. Write the fields from the table below as JSON into Request content and map the LinkedIn values. If the answers look empty, expand Mappable answers in the trigger output and map from there.
  6. Run the scenario once, then switch it on.

Field mapping

FieldWhat to map from LinkedInNotes
emailEmail addressUsed to find an existing contact. Email or phone is required.
firstNameFirst name
lastNameLast name
phonePhone number
companyCompany nameSaved as the contact's employer.
jobTitleJob title
tagsType a fixed text, for example LinkedIn Event OctSeveral tags separated by commas. Up to 10.
sourceType linkedin_lead_formShown in the delivery list, so you can tell sources apart.
consentYour consent checkbox answerOnly true, yes or 1 counts as marketing consent.

Common spellings work too, for example Email Address, first_name or Company Name, so you can often map LinkedIn's field names directly. Fields meetergo does not know are ignored.

A minimal JSON body looks like this:

{
  "email": "ada@example.com",
  "firstName": "Ada",
  "lastName": "Lovelace",
  "company": "Analytical Engines",
  "jobTitle": "CTO",
  "tags": "LinkedIn Event Oct",
  "source": "linkedin_lead_form",
  "consent": true
}

What happens with each lead

  • New email: a new contact is created with the fields you sent and your tags.
  • Known email: the existing contact gets the new tags and any field that was still empty. Fields that already have a value are never overwritten, and empty values never erase anything.
  • Consent: marketing consent is only recorded when consent is explicitly true. A missing or false value records nothing and keeps any consent the contact gave elsewhere.

The tile's dialog lists the last 20 deliveries with their result. A failed delivery shows the reason, for example a missing email address.

Start a sequence or reminders from the tag

  1. Open Newsletter → Sequences and create a sequence.
  2. Choose the trigger When a contact gets a tag and pick the tag you send from Zapier or Make.
  3. Add your mails, for example a confirmation right away and a reminder the day before the event, and activate the sequence.

When something does not work

What you seeWhat it means
404 from Zapier or MakeThe URL is wrong, was replaced with New URL, or turned off. Copy the current URL again.
400 with "Send an email or a phone number."The email field was not mapped or arrived empty. Check the mapping.
403Your plan no longer includes webhooks.
413The request was larger than 32 KB. Send only the fields from the table.
429More than 60 leads in one minute. Zapier and Make retry later.
The Zap tests fine but real registrations do not arriveCheck that the LinkedIn account connected in Zapier is an admin of the company page that owns the event.

Alternatives without Zapier

  • Import LinkedIn event attendees brings in the people attending your event as LinkedIn leads, without their form answers or email addresses.
  • n8n and any other tool that can send an HTTP POST work with the same URL and fields.

Was this article helpful?

Let us know if this article answered your questions.