flomo MCP integration for AI agents.
Connect AI agents to flomo through 13 structured actions, including get daily review, create memo, and memo recommended. Review authentication, inputs, workf…
- ACTION CONTRACTS
- 13
- AUTHENTICATION
- API key + Custom credentials
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the flomo integration exposes
The flomo Agent App exposes 13 provider-backed actions for productivity work. Its current contract lets an authorized agent fetch flomo daily review content through the flomo max mcp server, create a flomo memo by sending markdown or plain text to the incoming webhook, and find flomo memos related to a target memo through the flomo max mcp server. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key and Custom credentials. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected flomo account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real flomo capabilities.
Showing 12 of 13 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_daily_reviewREADFetch flomo daily review content through the flomo Max MCP server.
create_memoWRITECreate a flomo memo by sending markdown or plain text to the incoming webhook.
INPUTS: content / contentType / format
memo_recommendedREVIEWFind flomo memos related to a target memo through the flomo Max MCP server.
INPUTS: id / limit / no_same_tag
get_format_guideREADFetch flomo memo formatting guidance through the flomo Max MCP server.
get_tag_guideREADFetch flomo tag usage guidance through the flomo Max MCP server.
memo_batch_getREADFetch multiple flomo memos through the flomo Max MCP server in a single tool call.
INPUTS: id / ids
memo_searchREADSearch flomo memos through the flomo Max MCP server by keywords, tags, time range, or semantic search options.
INPUTS: keywords / tag / start_date / end_date / from
memo_updateWRITEUpdate an existing flomo memo through the flomo Max MCP server. The exact arguments are validated by flomo MCP.
INPUTS: id / content / format / local_updated_at
memory_contextREVIEWRead the generated flomo memory context through the flomo Max MCP server.
memory_userREVIEWRead the generated flomo memory user profile through the flomo Max MCP server.
tag_renameREVIEWRename flomo tags through the flomo Max MCP server and update associated memos.
INPUTS: old_tag / new_tag / max_memos
tag_searchREADSearch flomo tags through the flomo Max MCP server.
INPUTS: keywords / limit
INPUT CONTRACTS
Know what the action needs before it runs.
create_memo
contentREQUIRED- The memo content to publish to flomo.
contentTypeOPTIONAL- Set to `markdown` to send flomo webhook `content_type: markdown`; this is mapped to MCP `format` when custom_credential auth is used.
formatOPTIONAL- The flomo MCP content format, such as `markdown`.
memo_recommended
idREQUIRED- The target memo ID.
limitOPTIONAL- Maximum number of related memos to return.
no_same_tagOPTIONAL- Whether to exclude memos that share the same tag.
memo_batch_get
idOPTIONAL- One memo ID to fetch.
idsOPTIONAL- Memo IDs to fetch, as an array or comma-separated string.
memo_search
keywordsOPTIONAL- Keywords to search for in memo content.
tagOPTIONAL- Only return memos with this tag.
start_dateOPTIONAL- Only return memos created on or after this date.
end_dateOPTIONAL- Only return memos created on or before this date.
fromOPTIONAL- Only return memos from this source type.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Daily Review
Fetch flomo daily review content through the flomo Max MCP server. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_daily_reviewControl Create Memo
Create a flomo memo by sending markdown or plain text to the incoming webhook. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_memoVerify with Get Format Guide
Fetch flomo memo formatting guidance through the flomo Max MCP server. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_format_guideSAFETY BOUNDARY
Operate flomo with explicit limits
- Authorize flomo with API key and Custom credentials and grant only the provider access required by the selected actions.
- 2 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in flomo rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the flomo task completed successfully.
CONNECTION MODEL
API key + Custom credentials
Paste your dedicated flomo incoming webhook URL. You can copy it from https://flomoapp.com/mine?source=incoming_webhook.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 6
- WRITE SIGNALS
- 2
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 5
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by flomo.