a linkedin assistant with a specific set of tools

what a bot can do in LinkedIn

linkedin gives a bot a short list of tools, so be specific: name the post or company you mean. it can look up a profile or a company, but it can't search for people.

composio, the connection service dusk bot uses for apps, lists 29 LinkedIn actions (catalog version 20261101_00, read 12 november 2026⁴). dusk bot treats 15 of them as reads, 7 as sends and the other 7 as changes. an action counts as a read only when its name starts with a read word like get, list or search, so a bot you allow only to read can never call the rest. a send is anything that reaches a person outside the app or moves money, like create article or url share: it waits for your Allow unless you've given that bot a daily amount it may send alone.

connect LinkedIn

1. open Connected apps in the sidebar.
2. pick LinkedIn and sign in on LinkedIn's own page, so your password goes to them and never to a bot.
3. choose which bots may use it, and whether each may only read or may also change things. your bookkeeper doesn't need your LinkedIn.
4. ask in plain words. reading and drafting happen freely; sending asks you first.

connect linkedin and ask the bot to confirm its identity before preparing posts. start with reading for a page review, and supply the post references or company details it should inspect. having an action doesn't mean you can see every company's private stats; the bot only gets what your linkedin account can see.

routines to copy

these scheduled jobs begin with posts or organisations you identify. they do not depend on a general feed reader, inbox watcher or prospect search. the suggested copy stays in dusk bot chat.

every monday at 11, retrieve the available page statistics for the linkedin organisation i specified. describe the returned measures and their reporting period. flag missing data and avoid attributing changes to a campaign without evidence. do not change or publish anything.

every wednesday at 2, read the linkedin post references i keep in this chat. propose a follow-up to one that leaves a useful question open. include the source post, the question and proposed wording here. do not publish or comment.

each month on the first day at 10, retrieve the linkedin company information for the company i named. compare its returned description with the approved description i gave you. list wording differences for our review without claiming you can edit the company page.

what it asks you first

creating posts and sending comments asks first under dusk bot's default sending setting. a daily allowance can let a bot send within the amount you choose, so keep asking enabled if every public word needs your review. one exception: a bot on Full access with no sending rule of its own may send up to 25 a day without asking, so give full-access bots Ask every time under sending. preparing proposed wording in your chat is separate from publication.

read-only access blocks uploads, publishing and deletion actions. if you enable changes, do not treat a sending approval as a promise that every other action asks too. use an exact allowed action list, and write "ask me before you change anything" when you want broader review of changes.

what it cannot do

• read or send linkedin inbox messages through this toolkit. there is no direct-message action among the 29 listed actions.
• send connection requests or run a general people search here. the ad targeting search action is not a substitute for either.
• promise a full feed or comment-inbox digest. the catalog has specified post retrieval, reactions and comment creation, but no general feed reader or comment-listing action.
• start a routine when something happens on linkedin. there are no linkedin event triggers, so these routines run on a schedule.
• run the scheduled page review when your local computer is sleeping. use dusk cloud if the job needs to continue with your desktop off.

content work needs sources you can point to

supply the post references and the approved company wording. that gives the bot something concrete to compare instead of asking it to invent what your company should say. for social media posting, decide on a review step before allowing publication.

if your goal is lead research, separate that research from this connector. these actions can't find people, email addresses or phone numbers.

ask for a smaller statistics brief

choose the measures your team already uses and ask for the reporting period beside them. a change in reactions is not proof of sales impact. if the statistics action fails or returns only part of the request, the useful result is a clear gap to investigate.