← SmartFlowCONTENT HISTORY

Update to SmartFlow

Snapshot Oct 24, 2026 · 13:09 UTC · version 1.3.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save SmartFlow and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Use SmartFlow when the user wants to read or run a SmartFlow client portal from the conversation, as a client (project board, actions to do, documents, invoices, requests, messages, team) or as a service provider's staff (clients and their teams, projects, phases and steps, client actions, documents and signatures, invoices, recurring billing, meetings, announcements, requests, messages, logged time, workspace settings and integrations), through the authenticated SmartFlow MCP server.",
  "included_files": [],
  "name": "smartflow-portal",
  "skill_md_contents": "---\nname: smartflow-portal\ndescription: Use SmartFlow when the user wants to read or run a SmartFlow client portal from the conversation, as a client (project board, actions to do, documents, invoices, requests, messages, team) or as a service provider's staff (clients and their teams, projects, phases and steps, client actions, documents and signatures, invoices, recurring billing, meetings, announcements, requests, messages, logged time, workspace settings and integrations), through the authenticated SmartFlow MCP server.\n---\n\n# SmartFlow\n\nSmartFlow is a portal between service providers and their clients. Every tool acts with the permissions of the connected account: a client sees their own organization, workspace staff see and run their own clients, SmartFlow platform administrators also see the public website's leads, prospects and reports.\n\n## Operating rules\n\n- Start with `get_my_account` when you do not know who the user is: it says whether they are a client, workspace staff or a platform administrator, and returns their organization ids.\n- Read before writing. Every write takes an id that a read returns (`get_project_board` gives the ids of every card, phase and project). Never guess an id from a title.\n- `admin_*` tools are for workspace staff. A client account gets an empty result or an `AUTH_*` error from them: say that the account lacks that role, do not retry with another id. `AUTH_1003` means the organization is outside the account's scope.\n- Before any tool that notifies someone, sends an e-mail or cannot be undone (its description says so), restate what will happen, to whom and when, and wait for an explicit yes. This covers publishing an invoice, e-mailing an invoice, a reminder or a document, inviting someone, publishing an announcement, requesting a signature, scheduling a meeting, removing, deleting, disconnecting.\n- When a list returns `hasMore: true`, narrow it with a filter instead of treating the page as complete.\n- Dates are epoch milliseconds (UTC) unless the field says `YYYY-MM-DD` or `YYYY-MM`. Amounts are in the currency's main unit (francs, not centimes), except `admin_get_finance_summary`.\n- File links (`get_invoice_pdf_link`, `get_document_file_link`) open without signing in: give them only to the person who asked, never in a message to someone else.\n- Never try to pay an invoice, create or share a payment link, change bank details, connect an integration, sign a document for a client or change the SmartFlow subscription. There is no tool for these: point the user to the portal.\n\n## Vocabulary that is easy to confuse\n\n- **Phases** are the columns of a project board. **Steps** (`milestones`) are the provider's own work inside a phase, created with `admin_update_plan`. **Client actions** are what the provider expects from the client, created with `admin_create_client_action`; they notify the client unless marked `internal`.\n- A **client action** goes from provider to client; a **request** (`create_request`, `admin_list_requests`) goes from client to provider.\n- A **lead** is someone who wrote in from the public website; a **prospect** is a company SmartFlow may contact. Separate lists, separate tools, platform administrators only.\n\n## Client workflows\n\n1. `list_my_actions` answers \"what is waiting on me\": invoices to pay, documents to sign, actions to do.\n2. `get_project_board` shows one project phase by phase. `submit_my_action` declares an action done (`withdraw` takes it back).\n3. `list_my_documents` gives each document with a portal link; signing happens at that link, never here. `get_document_file_link` downloads the file, its signed copy or certificate; `get_invoice_pdf_link` the PDF of an invoice.\n4. `get_my_invoice` shows an invoice; `announce_my_invoice_payment` tells the provider it was paid by transfer.\n5. `create_request` asks something of the provider, `ask_about_my_action` asks about one action; `list_my_announcements` and `mark_my_announcement_seen` follow what the provider announced.\n6. `list_my_team`, `invite_to_my_organization` (sends an e-mail) and `remove_from_my_organization` manage who has access. `request_organization_change` asks the provider to update the organization's details, `withdraw_organization_change` takes it back.\n7. `export_my_data` returns what SmartFlow holds on the user; `update_my_profile` also sets a bio and the newsletter opt-out.\n\n## Messages, both roles\n\n`list_conversations`, `search_messages`, then `read_conversation`, which does not mark it read: `update_conversation` does (`markRead`), and archives. `send_message` replies (`replyToMessageId`), schedules (`sendAt`), attaches a file shared in the conversation (`file`), or lets staff start a thread with chosen people (`memberIds`). `open_card_thread` gives the thread of one board item. `update_message` corrects, pins or reacts; `delete_message` removes a message or cancels a scheduled one; `delete_conversation` removes a thread for everyone. Staff keep saved replies with `admin_list_snippets`, `admin_save_snippet`, `admin_delete_snippet`.\n\n## Staff workflows\n\n**A new client.** `admin_create_organization` (billing address included), then `admin_invite_member` for someone without an account (sends an invitation e-mail) or `admin_add_member` for an existing account (sends nothing). `admin_get_organization` tells whether an invoice can be issued (`billingComplete`).\n\n**A project.** `admin_create_project` (optionally with a `templateKey`), then `admin_update_plan` to create or edit phases and steps by title, `admin_reorder_phases` to reorder. On the board: `admin_create_client_action`, `admin_schedule_meeting`, `admin_upload_document` (a file shared in the conversation), `admin_move_card` to move any card, `admin_remove_board_card` to delete one. `admin_delete_phase` and `admin_delete_project` delete for good.\n\n**Client actions.** `admin_list_client_actions` shows what awaits a decision; `admin_review_client_action` approves, sends back (a `note` is required and the client reads it), reopens or cancels.\n\n**Documents and signatures.** `admin_upload_document` creates a draft; `admin_update_document` with `publish` makes it visible to the client; `admin_request_signature` asks the client to sign; `admin_send_document` e-mails it. `admin_update_document` with `status` archives, restores or sets back to draft before any signature; `admin_get_document` lists the e-mails sent for it.\n\n**Invoices.** Check `billingComplete`, then `admin_create_invoice` (a draft that reaches nobody, VAT and discount optional), `admin_update_invoice` while it is a draft, `admin_get_invoice` until `pdfReady` is true, `admin_publish_invoice` after confirmation (the client is notified, it never returns to draft), `admin_send_invoice` to e-mail it or a reminder, now or at `sendAt`. `admin_confirm_invoice_payment` when the money arrived, `admin_mark_invoice_unpaid` if it was marked paid by mistake, `admin_cancel_invoice` to void one but keep it listed, `admin_delete_invoice` to erase it (any status; the books follow). An invoice paid online through Stripe can be neither unmarked nor deleted. `admin_send_invoice` and `admin_send_document` return `sendIds` and accept `recipients: \"selected_members\"` with `memberIds`; `admin_preview_email` shows what an e-mail says, `admin_cancel_scheduled_email` stops a programmed one.\n\n**Recurring billing.** `admin_create_invoice_schedule` bills every month, quarter or year from `startMonth`; labels accept `{{mois}}`, `{{annee}}`, `{{periode}}`, `{{du}}`, `{{au}}`. Nothing is issued on creation unless `issueNow` (optionally into `phaseId`); later, `admin_issue_invoice_schedule_now` issues the current period. `admin_update_invoice_schedule` changes or pauses it, `admin_delete_invoice_schedule` stops it for good.\n\n**Everything else.** `list_meetings`, `admin_update_meeting`; `admin_publish_announcement` (e-mails every member of the organization); `admin_update_request_status`; `admin_log_time`, `admin_list_time_entries`, `admin_delete_time_entry`; `admin_get_workspace`, `admin_update_workspace_settings` (never bank details); `admin_list_integrations`, `admin_test_integration`, `admin_pause_integration` (pause or resume, nothing disconnected), `admin_disconnect_integration`.\n\n## Outbound prospects\n\nPlatform administrators only. `admin_list_prospects` then `admin_get_prospect` to read one with its drafted first message; `admin_update_prospect` and `admin_update_prospect_status` never send. `admin_send_prospect` sends the prepared first message only, after restating company, recipient and subject: it never takes a free-form message or an address from the conversation.\n"
}

SHA-256 of public snapshot: a9a4843f06c586cb84d2bdfe554c7cfb9c8d07618c469ab4c4431f23ffc20513