comment-linkedin-post) and Reply to Comment
(reply-linkedin-comment) can publish as a managed LinkedIn company Page.
Leave company selection absent to keep using your personal connected account.
Choose the account and Page
Use List accounts to select the exact connected LinkedIn account. In AI Chat, use List LinkedIn Managed Pages (list-linkedin-managed-pages) for
that account and choose the intended Page. If several accounts or Pages match,
clarify which one to use.
Copy the complete returned binding into company:
Comment or reply
Keep your existing post URL, post ID or latest-post targeting and manual or AI comment settings. Existing topic filters and age rules continue to apply. For replies, usereplyToUrl for the existing commenter targeting, or provide
an exact parent commentId with company selection. The parent is checked
within the selected post. Conflicting commenter and parent selections stop
the action.
In AI Chat, the confirmation identifies the connected account, Page, resolved
post, parent comment for replies, and exact comment text. AI-generated text is
prepared before approval and remains fixed for that approved call. Cancel or
Escape posts nothing. An ordinary workspace tool grant does not approve a
different company comment.
Existing {{post_owner}} and {{comment_owner}} individual mentions remain
available. Company-author mentions with numeric IDs are not currently supported
in Page comments; edit the mention before sending. Text is never silently
changed to remove an unsupported mention. No comment attachments are added.
Save a Workflow
Workflow Actions and Workflow Agents support the same company selection. Save or map the connected account and the completecompany binding. You can
map the whole binding, its individual fields, or a complete JSON binding.
Leave the optional Company Page field unset for personal behavior; an empty
or incomplete supplied object is an invalid company selection.
The step author must remain a workspace member with access to the account.
For a manually started run, the starter’s account access also applies. Each
run rechecks Page administration. Workflows reuse those authorization services
internally; the managed-Page discovery, invitation and allowance tools remain
AI-only. This does not add company comments to Records columns or programs.
Use commentingIdentity.accountId, .id, .name and .type in downstream
steps to identify the provider-confirmed commenting Page. postUrl, text and
repliedToCommentId remain available as before. requestedCommentingIdentity
identifies the requested Page when acceptance could not be established.
Results and retries
commented or replied means LinkedIn returned the expected comment with the
selected company author. It does not independently verify public propagation.
skipped preserves the existing age, filter and duplicate checks. refused
means the provider rejected the write. uncertain means it may have accepted
it; commentingIdentity is then null, and outcomeUnconfirmed is true.
Keep the original invocation key on retries. The exact account, company,
post/parent and content are bound to the action. Accepted and uncertain writes
are retained as terminal receipts; never automatically replay an uncertain
write. Check the exact destination before a separate explicit action.
Existing configured tool billing, AI usage accounting and rate limits apply.
Receipt replays and definite provider refusals report no additional tool cost.
Authorized MCP and ChatGPT clients use the existing tool discovery, account
selection and invocation controls. General account permissions still apply.