LinkedIn Events
Social MediaConnect AI agents to the LinkedIn Event Management API. Agents create and update LinkedIn events and read their details as part of a broader campaign flow.
What This Integration Enables
The LinkedIn Event Management API is the least forgiving integration in this catalog, and building on it well means designing around its lifecycle rather than around the convenience of a single create call. Events come in three types: Live Video streamed on LinkedIn, External streamed on another site, and In-Person at a physical venue. Create Event sets the name, organizer, start time, and the type-specific fields, and optionally attaches a lead generation registration form, a background image, a vanity name, a description, and a discovery mode. Post Event then publishes it through the Posts API, which is the step that makes the event publicly visible. Get Event, Find Events by Organizer, and Find Lead Gen Form Events by Organizer read the estate afterwards, with the finders supporting lifecycle state, entry criteria, time windows, sorting, and pagination. Update Event applies a partial update to the mutable fields, and Delete Event removes an event by deleting its associated post.
Four behaviors decide whether a flow works here, and none of them are guessable from the action names. First, Create Event freezes the organizer, the event type and format, the lead gen form, and the test flag permanently. Update Event cannot touch any of them. Second, an event does not exist publicly until Post Event runs, and until it does it cannot be fetched by Get Event, cannot be updated, and cannot be deleted, and the finders return only posted events, so an unposted event is invisible to the API that created it. Third, Update Event works only after the event is posted and only while it has not yet started, so once the original start time passes or the event is cancelled, updates are rejected. Fourth, registration data does not come from here at all: there are no attendee or event role endpoints, and registrants are retrieved through the Lead Sync API using the lead gen form attached at creation, which is why LinkedIn Lead Forms is the sibling service that completes this picture. Access is gated too. The Event Management API is a self-serve product that developers apply for separately from the Marketing API Program, the connected member must hold an ADMINISTRATOR or CONTENT_ADMINISTRATOR role on the organizer page, and this connector ships no triggers because LinkedIn publishes no event subscription here. A flow is started by the campaign calendar, not by LinkedIn.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The webinar that exists in one place and appears in two
A quarterly webinar is approved in the campaign calendar with a date, an organizer page, a title, and a registration requirement. A flow resolves the organizer URN, calls Find Events by Organizer filtered to Upcoming to confirm nothing already exists for that slot, and assembles the full Create Event payload including the lead gen form specification. It sends the assembled record to the campaign owner for approval rather than creating it. On approval, Create Event runs, the response yields the live video URN for a Live Video event, and Post Event publishes it using that URN as the content reference. The event id and vanity name are written back to the campaign record, so the internal calendar and LinkedIn hold the same object rather than two loosely related ones.
Registration that reaches the CRM instead of a spreadsheet
Registrants never appear in this connector, and building around that constraint is the whole trick. A weekly flow calls Find Lead Gen Form Events by Organizer, which returns each event along with its versioned lead gen form URN. Those URNs are handed to the Lead Sync path through LinkedIn Lead Forms, the responses are matched against existing records, and new registrants are created or updated in HubSpot with the event as the source. The finder exists precisely because the lead gen form URN is the join key between an event and its registrants, and this flow uses it as the bridge rather than asking a person to export a list.
A weekly reconciliation of the event estate
Marketing teams accumulate LinkedIn events across several organizer pages and lose track of which are still upcoming. A scheduled flow calls Find Events by Organizer for each page the connected member administers, filtered to Upcoming and excluding cancelled events, and calls Get Event on each result for the full record including start times, discovery mode, and lead gen form. It compares that against the campaign calendar and reports three differences to the marketing owner in Slack: events on LinkedIn with no campaign record, campaign records with no LinkedIn event, and events whose start time has drifted. Nothing is corrected automatically, because Update Event stops working once an event's start time passes and a correction attempted too late fails silently in the flow rather than loudly on the page.
Human-in-Loop Highlight
On most connectors the approval gate goes in front of the publish. Here it goes in front of the create, and the reason is a genuine trap in the API's lifecycle. Create Event permanently freezes four fields: the organizer, the event type and format, the lead gen form, and the test flag. Update Event cannot change any of them. And an event that has not been posted cannot be fetched with Get Event, cannot be updated, and cannot be deleted, because Delete Event works by deleting the event's associated post and an unposted event has none. So a Create Event call with the wrong organizer page or without the lead gen form leaves exactly one escape route: run Post Event to publish the mistake, then Delete Event to remove it. The remedy requires making the error public first. So the agent assembles the entire payload, checks the organizer estate with Find Events by Organizer, and stops: "Ready to create 'Q4 Platform Briefing' as a Live Video event on the Northwind Systems page for 12 November, with a templated lead gen form. Organizer, event format, and lead gen form are frozen at creation, and an unposted event cannot be edited or deleted. Confirm before I create it?" The last genuinely reversible moment on this connector is the one before the create call, and that is where the gate belongs.
Agent Capabilities
7 actionsEvents
7- Get Event Retrieves a single event by its numeric id, returning the full record: name, description, organizer, start and end times, type with its type-specific sub-fields, vanity name, discovery mode, background image, lead gen form, and the associated ugcPost URN. An event is only fetchable after it has been posted, and fetching an unposted event returns an error.
- Find Events by Organizer Lists the events organized by a given organization or person, with server-side filtering and sorting. Restrict by lifecycle state of Upcoming, Ongoing, or Past, or by an explicit start-time window, filter by entry criteria of Public or Gated, exclude cancelled events, sort by start time or end time, and page with Start and Count. Only posted events are returned.
- Find Lead Gen Form Events by Organizer Lists all events organized by a given organization that have a lead generation form attached, each with its versioned lead gen form URN. Those URNs are the join key to registrant data through the Lead Sync API, which makes this the action that turns an event into a lead source.
- Create Event Creates a Live Video, External, or In-Person event. Sets the name, organizer, start time, and type-specific fields, and optionally attaches a lead generation form by privacy policy URL for a templated form or by an approved lead gen form URN, plus a background image, a vanity name, a description, and a discovery mode. Supplying both a privacy policy URL and a lead gen form URN is an error. The organizer, event type and format, lead gen form, and test flag cannot be changed afterwards, and the created event is not visible, fetchable, updatable, or deletable until Post Event runs.
- Update Event Partially updates a posted event's mutable fields: name, description, vanity name, start time, discovery mode, background image, and the type-specific end time, external URL, address, and venue details. Only supplied fields change, the event type must match the event's actual type so nested fields resolve correctly, and updates are rejected once the original start time has passed or the event is cancelled.
- Post Event Publishes a created event through the Posts API, which is the required step that makes it publicly visible and therefore fetchable and updatable. For a Live Video event use the live video URN from the Create Event response as the content reference; for External and In-Person events use the event URN. Afterwards the event's ugcPost field is populated, which Delete Event needs.
- Delete Event Deletes a posted event by deleting its associated LinkedIn post, using the event's ugcPost URN. An event cannot be deleted until it has been posted, so this is not an escape hatch for a bad creation until the creation has already been published.
Frequently Asked Questions
What can FlowRunner do with LinkedIn Events?
FlowRunner agents can run Get Event, Find Events by Organizer, and Find Lead Gen Form Events by Organizer in LinkedIn Events, plus 4 more actions.
Does connecting LinkedIn Events to FlowRunner require OAuth?
Yes. LinkedIn Events connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.
Can LinkedIn Events trigger a FlowRunner workflow automatically?
LinkedIn Events doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with LinkedIn Events
$100 in credits. No card required. Connect in minutes.