# Workday

Connect LinkedIn to Workday with Linked API through Make or the API – LinkedIn profile data and events flow into your HR workflows. No native Workday app.

There is no native Linked API app for Workday. You connect the two today through [Make](/integrations/make/overview), whose Workday Human Capital Management app is available on Make's Enterprise plan and needs a Workday admin to set up an integration user, or through the [Linked API](/docs/core-concepts) from your own code. n8n has no Workday node, so in [n8n](/integrations/n8n/overview) the Workday side runs through its HTTP Request node and Workday's own APIs.

Linked API works from the recruiter's own LinkedIn account: it searches and reads profiles, sends connection requests and messages, and reports what happens in the inbox and network. The logic that ties this to Workday lives in your Make scenario, your n8n workflow or your code – nothing is installed inside Workday.

## LinkedIn profile data into Workday

A scenario reads a person's profile with **Fetch Person** (headline, experience, education, skills) and passes the fields to Workday – in Make, for example, through the Workday HCM modules for pre-hires; elsewhere through Workday's APIs.

## LinkedIn events into your HR workflow

Linked API sends LinkedIn events to a [webhook](/docs/webhooks) – a custom webhook in Make, a Webhook node in n8n, or your own endpoint – and the scenario decides what to update or whom to notify.

- `inbox.messageReceived` – a candidate replied on LinkedIn. Needs [inbox monitoring](/docs/monitoring-inbox), switched on once with Sync Inbox.
- `network.connectionAccepted` – a candidate accepted your connection request. Needs [network monitoring](/docs/monitoring-network), switched on once with Sync Network.
- `workflow.completed` – an action you started finished, with its result.

Linked API picks up new messages and connections on periodic syncs, so an event arrives shortly after it happens on LinkedIn, not the same second. One webhook receives every event you choose, so branch on the event `type` – a router in Make, a Switch node in n8n. The full list is on [Event Types](/docs/webhook-event-types).

## Outreach from the recruiter's account

From a candidate's LinkedIn URL, a scenario can **Send Connection Request** (with or without a note) or **Send Message** to someone who is already a connection. The same account is also open to an AI assistant through [MCP](/mcp/overview) or the [CLI](/cli/getting-started), for example to screen profiles against a requisition.

## What this does not cover

- **Anything inside Workday's interface.** There is no Linked API panel or notification in Workday; results arrive as the records your scenario writes.

## Get started

1. Connect Linked API in [Make](/integrations/make/creating-connection) or [n8n](/integrations/n8n/creating-credential).
2. Register your [webhook](/docs/webhooks) and choose the events it receives.
3. Add the Workday HCM modules in Make – or the HTTP Request node in n8n – and map the fields.
