# LinkedIn Lead Gen Forms + Krokul CRM

Yes. Krokul CRM integrates with LinkedIn Lead Gen Forms. Every form response becomes a contact, a client company and a deal in Krokul, with the campaign and form as its source, and job title, company size and other answers arrive with the deal. The route runs through the Krokul app in Zapier or Make, or through the Krokul API and webhooks.

**Status:** Via API and webhooks. **Automation platforms:** Zapier, Make.

## What your team gets

### A sponsored form response opens a deal

A buyer submits the form attached to your sponsored content or message ad. LinkedIn notifies Krokul through its leadNotifications subscription, and Krokul reads the response from leadFormResponses. It then finds or creates the contact by email, links the client company by name and opens a deal with the source set for that form.

### Job title and company size reach the manager

LinkedIn forms usually ask for job title, seniority or company size. Krokul maps these answers to contact fields and custom deal fields, so the manager knows who is on the other side and how large the company is before the first call.

### Event and organic forms on their own pipeline

LinkedIn separates form responses by where they came from, which can be ads, event pages, company pages or product pages. Krokul routes each type to the pipeline you choose, so registrations for an event do not mix with replies to paid campaigns.

### Won and lost deals shape the audience

With the Krokul app in Zapier, the Krokul events Deal Won and Deal Lost drive LinkedIn Ads audience actions. Remove Email from Audience takes out people who already bought, and Add Contact to Audience builds a list for a follow-up campaign.

## What moves between LinkedIn Lead Gen Forms and Krokul

| LinkedIn | Krokul | Direction | When |
|---|---|---|---|
| leadNotifications event | Incoming request for the connected ad account | LinkedIn → Krokul | Each new form response |
| leadFormResponses: name, work email, phone | Contact, matched by email or phone | LinkedIn → Krokul | Read right after the notification |
| leadFormResponses: company name | Client company on the contact | LinkedIn → Krokul | Same response |
| leadFormResponses: job title, company size, custom questions | Contact fields, custom deal fields and first message | LinkedIn → Krokul | Same response, by the form mapping |
| Form, campaign and response type | Pipeline, source and campaign tags of the deal | LinkedIn → Krokul | Same response |
| Matched audience | Won or lost deal and its contact | Krokul → LinkedIn | Krokul app in Zapier, audience actions |

## How to connect today

### Krokul app in Zapier or Make

1. Connect the Krokul app with an API key.
2. Use the Krokul triggers Deal Won and Deal Lost with the LinkedIn Ads actions Add Contact to Audience and Remove Email from Audience.
3. Start from the LinkedIn Ads trigger New Lead Gen Form Response (Sponsored content) or New Lead Gen Form Response (Organic Content) and run the Krokul actions Find Contact and Create Deal, with one route per form.

### Custom flow through the Krokul API and webhooks

1. Get a Krokul API key with write scopes for contacts, client companies and deals.
2. With Lead Sync API access from LinkedIn, subscribe to leadNotifications and read each response from leadFormResponses.
3. Call contact/api-find, then clientCompany/api-create and card/api-create, and store the LinkedIn response ID on the deal with externalRef/api-upsert.
4. To feed audiences back, subscribe a Krokul webhook to card.won and card.lost and check its x-crm-signature header before you call LinkedIn.

**Triggers:** New Lead Gen Form Response (Sponsored content); New Lead Gen Form Response (Organic Content).

**Actions:** Add Contact to Audience; Add Company to Audience; Create Audience; Remove Email from Audience; Create Report.

### For integrators

LinkedIn runs its Lead Sync API separately. Reading responses requires the r_marketing_leadgen_automation permission, and access to the Advertising API does not include it. If you build your own route with that access, your handler can call contact/api-find, clientCompany/api-create, card/api-create and externalRef/api-set in the Krokul API with a bearer key, passing the LinkedIn response ID to the last one. Krokul webhooks are signed and logged, and a sandbox company keeps tests apart.

[API documentation](https://app.krokul.com/api/v1/docs)

## Questions and answers

### Does Krokul integrate with LinkedIn Lead Gen Forms?

Yes. Krokul integrates with LinkedIn Lead Gen Forms through the Krokul app in Zapier and Make, and through its API and webhooks.

### Which LinkedIn forms reach Krokul?

LinkedIn syncs form responses of four types, which come from ads, event pages, company pages and product pages. LinkedIn notes that new forms on Pages and Showcase Pages can no longer be created, while existing ones keep working.

### Does my team need its own LinkedIn API access?

Not for Zapier or Make. There your team signs in to LinkedIn with an account that can see the ad account or the page. A custom flow that reads leadFormResponses directly needs the separate Lead Sync API access.

### Does Krokul send anything back to LinkedIn?

Through the Krokul app in Zapier, won and lost deals update LinkedIn Ads audiences, so buyers leave a campaign and follow-up audiences grow from real outcomes.

## Limits

Campaigns, targeting and the forms themselves stay in LinkedIn Campaign Manager. Krokul takes the responses and runs the conversation and the sale that follow.

## Related services

- [Meta Lead Ads](https://krokul.com/en/integrations/meta-lead-ads/index.md)
- [Google Ads](https://krokul.com/en/integrations/google-ads/index.md)
- [Typeform](https://krokul.com/en/integrations/typeform/index.md)
- [Zapier](https://krokul.com/en/integrations/zapier/index.md)

[Forms and ad inquiries](https://krokul.com/en/integrations/category/lead-capture/index.md)

LinkedIn is a trademark of LinkedIn Corporation. Krokul is not affiliated with LinkedIn.

Updated: 2026-10-12

---

App: https://app.krokul.com/ · API: https://app.krokul.com/api/v1/docs