1
Quick scan
Use External Inbox and Requests to turn unstructured inbound work into something reviewable, triage-ready, and actionable.
External Inbox
Requests
Triage
Convert to task
2
Overview
Client work usually starts messy: a forwarded message, a connected Gmail or Slack item, assigned Jira work, or a quick Telegram request. Flopinio preserves the source in External Inbox so an operator can review it before creating a request, note, task, or other workspace record.
3
Capture first, structure second
Use External Inbox when the source should be preserved. Telegram, Gmail, Jira, and Slack connected-account flows keep provider context attached where configured. Manual requests are better when you already know the client, project, and ask. Browser Extension capture remains pending public marketplace publication.
4
Run triage when the ask is unclear
AI triage can suggest a summary, urgency, client, project, or next step. The operator still reviews and applies the result. This keeps the original client message available while turning it into a cleaner request.
5
Convert only when executable
A request should become a task when the deliverable is clear. If the input is only background, save it as a note. If it records an approved direction, create a decision.
6
Where automation fits
Accounting workspaces can accept recommended request triage or review automations. Those automations start review runs; they do not remove the final apply step.
7
Next steps
Read Requests help.
Read External Inbox help.
Common Questions
Should every external item become a request?
No. Some captures are notes, decisions, or tasks. Review the intent before creating records.
Can AI triage apply changes automatically?
No. The shipped flow stages suggestions for operator review.
Open the related workspace surface
Use the linked product area after reviewing the page guidance and permission notes.