> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Let AI Agents Post to LinkedIn on Your Behalf

> Let agents read your LinkedIn profile and create posts, comments, and reactions. Connect with OAuth, and keep publishing behind approval if you want.

## Overview

Buckle connects AI agents to LinkedIn through OAuth. Agents can read your profile, email, and create, modify, and delete posts, comments, and reactions. The gateway injects OAuth credentials into requests to the LinkedIn API automatically.

## What you will set up

* A LinkedIn connection through OAuth
* Automatic token injection on LinkedIn API requests
* Per-agent, per-tool access, such as approval before posting

## Setup

**1. Open the app**

Open the Buckle dashboard and navigate to **Settings** > **Apps** > **LinkedIn**.

**2. Authorize**

Click **Connect LinkedIn**. You'll be redirected to LinkedIn to authorize Buckle. Review the requested permissions and click **Allow**.

![Buckle connect window for LinkedIn on Cloud, showing the Connect to LinkedIn button.](https://mintcdn.com/onecli-17d3f772/h1DTAVlDkLshz4JZ/images/integrations/linkedin/buckle-connect-linkedin.png?fit=max\&auto=format\&n=h1DTAVlDkLshz4JZ\&q=85\&s=6c5915e3938afc41bc3a4859a350aaae)

The LinkedIn connect window on Buckle Cloud.

**3. Verify**

After authorization, you'll be redirected back to the dashboard. The connection will show as **Connected** with your LinkedIn email.

## What agents can do

| Area | Description |
| - | - |
| **Profile (read)** | View your name, photo, headline, and identity |
| **Email (read)** | Access your primary email address |
| **Posts & Reactions (write)** | Create, modify, and delete posts, comments, and reactions on your behalf |

## Use cases

* Content agents that draft and publish LinkedIn posts
* Engagement agents that respond to comments
* Social media scheduling agents that post on a schedule
* Agents that cross-post content from other platforms to LinkedIn

## Self-hosted: use your own LinkedIn app

> [!NOTE]
>
> **Skip this section on Buckle Cloud.** It's only for self-hosted Buckle without `LINKEDIN_CLIENT_ID` and `LINKEDIN_CLIENT_SECRET` set, or if you want your own company name on LinkedIn's consent screen.

> [accordion] 1. Create the LinkedIn app
>
> Go to the [LinkedIn Developer Portal](https://www.linkedin.com/developers/apps) and select **Create app**. Name it, link your company's LinkedIn Page, upload a logo, and create it.

> [accordion] 2. Add the products
>
> Open **Products** and request **Sign In with LinkedIn using OpenID Connect** and **Share on LinkedIn**. Together they grant the scopes Buckle requests: `openid`, `profile`, `email`, and `w_member_social`.
>
> ![LinkedIn developer app named Buckle on the Products tab, with Share on LinkedIn under Added products.](https://mintcdn.com/onecli-17d3f772/h1DTAVlDkLshz4JZ/images/integrations/linkedin/01-provider-setup.png?fit=max\&auto=format\&n=h1DTAVlDkLshz4JZ\&q=85\&s=bb1db02f2cf555282804b21b0b3c43ea)
>
> The Products tab of your LinkedIn app after adding Share on LinkedIn.

> [accordion] 3. Add the redirect URL
>
> In Buckle, open **Settings** > **Apps** > **LinkedIn** > **Custom credentials** and copy the **Redirect URI**. In LinkedIn, open **Auth**, add it under **Authorized redirect URLs for your app**, and save.
>
> ![Buckle Custom credentials card for LinkedIn with the setup guide link, the Redirect URI and its copy button, and the client ID and secret fields.](https://mintcdn.com/onecli-17d3f772/h1DTAVlDkLshz4JZ/images/integrations/linkedin/buckle-custom-credentials-linkedin.png?fit=max\&auto=format\&n=h1DTAVlDkLshz4JZ\&q=85\&s=12b55c44f92c69acffe69754cb5202ea)
>
> Copy the Redirect URI from Custom credentials in Buckle.

> [accordion] 4. Connect with your app
>
> On the **Auth** tab, copy the **Client ID** and **Primary Client Secret**. Paste both into **Settings** > **Apps** > **LinkedIn** > **Custom credentials**, select **Save credentials**, then **Connect** and allow access in LinkedIn.

## Controlling access

Access is per agent: [grant](/docs/guides/agent-access.md) the connection to each agent that needs it, choosing per tool what runs freely, what needs human approval, and what stays blocked — a read-only agent is a single grant. Organization [rules](/docs/guides/rules.md) add guardrails on top, like rate limits and blanket blocks. Everything is checked before credential injection, so a blocked request never reaches LinkedIn.

## FAQ

> [accordion] Can I approve LinkedIn posts before they go live?
>
> Yes. Put post creation behind approval when you [grant](/docs/guides/agent-access.md) the connection.

> [accordion] Does the agent see my LinkedIn token?
>
> No. The token stays in Buckle, and the gateway adds it at the proxy. See [How it works](/docs/how-it-works.md).

> [accordion] How do I reconnect LinkedIn?
>
> Open **Settings** > **Apps** > **LinkedIn** and connect again. Agents with access use the new connection automatically.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.