A first-degree connection can be unfollowed. Connie checks following separately
from connection degree. Existing messages, saved Records and mutual connections
are not proof that the account is connected to a person. Actions stay unavailable
while their required state is unknown. Use Refresh contact state to check again.
Remove connection and Block ask you to confirm the named person. Cancel
or Escape runs nothing. While saving, repeated submissions are disabled.
LinkedIn requires the connected account’s password for every unblock. Enter it
only in the secure Unblock dialog; Connie forwards it for that request and
does not save it in chat, contact history or operation receipts. The field clears
after the attempt. LinkedIn prevents blocking that person again for 48 hours.
LinkedIn may refuse an action because of account permissions, restrictions or
provider limits. Connie keeps the last confirmed state. If an action succeeded
but contact refresh is pending, do not repeat it. If the outcome could not be
confirmed, check LinkedIn before another change. No mutation retries automatically.
Only restrictions confirmed by a fresh conversation read change Inbox’s reply state.
These controls apply to provider-confirmed individual LinkedIn member
conversations. Group and company contacts are excluded; provider product access
and account permissions still apply.
Ask Connie
Ask Connie to check the relationship, follow or unfollow the person, remove the connection, or block them. Connie reads the selected conversation’s current relationship and retains the normal approvals, including the extra confirmation for removing a connection or blocking. In a workspace with agents and rooms, ask an agent instead: message it in its DM or in a room. For an unblock request, Connie verifies that the person is blocked and directs you to the secure Inbox dialog. Never send account passwords in chat. These Inbox-specific actions are not Workflow Actions or Records Action columns. The existing URL-based Follow action remains available to existing Workflows. For API/MCP clients, readinbox-linkedin-contact-state with the saved
conversationId, then use its exact state.userId as expectedUserId with the
same conversation. follow-linkedin-profile supports this Inbox mode;
unfollow-linkedin-profile, remove-linkedin-connection and
block-linkedin-profile use the same target. Removal and blocking also require
confirmed: true after the user confirms. unblock-linkedin-profile returns
requires_secure_input; it never accepts a password or performs the unblock.
Client catalog availability depends on the deployed release and published tool
metadata. Existing account, approval and credit rules apply; no fixed price is
implied by this guide.