Workflow Nodes

Internal tools for completing, failing, and managing workflow node execution.

Tools (5)

complete_node

Full name: campaignstack_complete_node

workflows:write

Report successful completion of a workflow node for a lead. Marks the lead entry as COMPLETED, pushes the lead to the next node(s) via edges, and logs the action for audit. Returns the IDs of next nodes the lead was pushed to.

Parameters

Name	Type	Required	Default	Description
entryId	string	Yes	—	(min length: 1)
payload	object	No	—

---

fail_node

Full name: campaignstack_fail_node

workflows:write

Report failure of a workflow node for a lead. Marks the lead entry as FAILED with an error message. For auth_expired: reverts lead to WAITING and marks LinkedIn account as expired. For rate_limit: auto-pauses the action type with a 1-hour cooldown. Use campaignstack_complete_node for successful completions.

Parameters

Name	Type	Required	Default	Description
entryId	string	Yes	—	(min length: 1)
error	string	Yes	—	(min length: 1)
errorType	auth_expired | rate_limit | not_connected | generic	No	—

---

store_conversation

Full name: campaignstack_store_conversation

workflows:write

Store direct messages (DMs/InMails) sent or received in LinkedIn’s messaging UI in the unified inbox conversation store. ONLY for messages exchanged in a private message thread. NEVER call this for post comments, comment replies, likes, or any other on-post activity: those are public engagement, not conversations, and storing them creates fake message threads in the user’s inbox. If your task was to comment on or like a post, do not call this tool at all; report the action via campaignstack_complete_node instead. Deduplicates against existing messages (same senderProfileUrn + body within 60s = skip). Creates a new conversation record if none exists for the accountId + leadId pair. Returns the number of messages stored and skipped.

Parameters

Name	Type	Required	Default	Description
leadId	string	Yes	—	(min length: 1)
leadSource	global | private	No	—	Optional. Leave it out unless you know which lead store the id came from: the server derives it from the leadId and ignores a value that disagrees.
accountId	string	Yes	—	(min length: 1)
threadId	string	No	—
messages	object[]	Yes	—

---

escalate_to_human

Full name: campaignstack_escalate_to_human

workflows:write

Hand a lead to a human instead of acting on it. Creates a pending_review notification in the workspace and parks the lead in the review queue with your reason. Do NOT reply or post when escalating (they are mutually exclusive). Use it when the work needs human judgement (pricing questions, sensitive topics, complex objections) or when a craft tool withholds its draft and tells you to escalate. For batched jobs pass entryId from the current lead object in the input array; single-lead jobs need no ids at all.

Parameters

Name	Type	Required	Default	Description
entryId	string	No	—	(min length: 1)
nodeId	string	No	—	(min length: 1)
workflowId	string	No	—	(min length: 1)
leadId	string	No	—	(min length: 1)
reason	string	No	—

---

extract_post_engagements

Full name: campaignstack_extract_post_engagements

content:write

Extract all engagement data (reactions, comments, reposts) from a LinkedIn post. Must be called AFTER using browser tools to click reactions count, repost count, and sorting comments to ‘Most Recent’. The extraction reads intercepted API data from the current browser session via Voyager GraphQL. Returns counts of extracted reactions, comments, and reposts.

Parameters

Name	Type	Required	Default	Description
platform	linkedin	Yes	—
postUrl	string	Yes	—	(min length: 1)
authorName	string	No	—
contentSnippet	string	No	—

---