Create posts, with or without an article, delete them, and comment on and react to posts, as yourself.
A LinkedIn connection gives a playbook's functions five operations of the LinkedIn API, from a document Auto ships, written from LinkedIn's Sign In with LinkedIn and Share on LinkedIn products. You sign in to LinkedIn and allow posting as you, and every post, comment and reaction is yours.
Available on Auto Cloud and on self-hosted runtimes.
What a playbook can do with LinkedIn
- Read who you are at LinkedIn: your name, photo, member id and primary email.
- Create a post of text alone, or of text with an article's link, and delete a post it made.
- Comment on a post, and react to one.
It reads no post, yours or anyone's: LinkedIn grants reading posts to the apps it approves alone. A post the playbook did not create is reached by the URN you give it, or by the URN in its address. No image or video is attached.
The tools, as the connection lists them
Tools that read: get_userinfo.
Tools that act: create_post, delete_post, create_comment and create_reaction.
An example workflow
Publishing the week's article the way your brand does. An event trigger starts the workflow when your agent records that an article is published, with its address. A lookup function reads the article's text through a Google Drive or Notion connection. A reasoning function writes three candidate posts in the brand's voice, with the rules in its prompt: the length, the one idea a post carries, no hashtags beyond two, the question it ends on. An interaction function sends the three to the author through a Slack connection and waits for a choice or an edit; the request expires after a day, which ends the run as unanswered and leaves nothing posted. Once the author answers, an interaction function posts the chosen text with the article's link through create_post, and the run records the post's URN, so a later workflow can comment on it. Every draft and the choice are in the run's history in Studio.
How to connect LinkedIn
- Sign in to LinkedIn and allow posting as you. The consent screen shows the permissions listed below.
Then:
- Ask your agent to connect LinkedIn to Auto, or open Settings, Agents, Connections in Auto Studio and choose LinkedIn.
- On the Studio page, check the service and its access, choose which playbooks may use the connection, and approve it.
- Have your agent check one small read through the connection before a function depends on it.
What it needs
- A LinkedIn member account. The connection posts as a member, not as a company page.
- Your agent connected to Auto and signed in as you, with permission to change your organization, if your agent adds the connection.
- On a self-hosted runtime, a LinkedIn app of your own with the Sign In with LinkedIn using OpenID Connect and Share on LinkedIn products, registered as the runtime's client, as Let people add connections sets out.
Permissions Auto asks for
- Read the member id that confirms the LinkedIn member who connects.
- Read the name and photo of the LinkedIn member who connects.
- Read the primary email address of the LinkedIn account of the member who connects.
- Create, change and delete posts, comments and reactions as the LinkedIn member who connects.
Good to know
LinkedIn issues no refresh token, so the connection works for 60 days and then breaks as a consent that has ended; Studio shows it as needing attention, and the person who added it reconnects. LinkedIn also documents no way to revoke a token, so removing the connection forgets the token without revoking it at LinkedIn. Keep the functions that post few and named, and give the connection to the one playbook that publishes, under Only select playbooks.