This page summarizes how agentic workflows work in Stood
Activities can be marked as agentic to indicate agents should handle them.
Admins configure stage activities in Manage Stage Activities; use markup:
+Xd: schedule date X days in the future (e.g., +7d)
+agent: sets agentic = true
On deal stage change, configured activities are created and markup is applied.
Only UI-generated activities (via stage markup or form) can be agentic; MCP activity creation is always agentic = false.
UI indicator: agentic activities show a robot emoji appended to the todo (🤖) in lists/cards.
Name: get_agentic_activities
Returns: TODO-only activities with agentic = true for the current team.
Use-case: Agent task queue for what to process next.
Name: done_activity
Purpose: Mark an activity as done by ID.
Users can create posts and rich Markdown documents attached to deals from the posts thread.
Document editor supports GitHub-flavored Markdown, preview, and copy-as-HTML.
Name: create_post
Author: Always recorded as agent when created via MCP.
Display: In threads, agent posts are labeled with the localized Agent label and a robot avatar.
Name: add_document
Creates a document post attached to a deal (Markdown in docContent, title in docTitle, summary as Quill Delta in content).
Author: Always recorded as agent when created via MCP.
MCP activity creation cannot set agentic = true (forced to false in server).
MCP get_agentic_activities returns TODO-only agentic items (not done/cancelled).
Posts & documents created via MCP always use author = agent; UI displays localized Agent name and robot icon.