← Plugin catalog
Business & Operations

SmartFlow

HUGO GEBEL v1.3.0

Client projects and invoices

Create a free account to save this plugin.

From the developer

Declared capabilities

  • Read project boards and plans
  • Track and submit client tasks
  • Manage clients and their teams

Cost & access

SmartFlow sells nothing in the conversation. No tool takes a payment or creates a payment link; that stays in the portal.

Declared limitations

  • The app should not act. No tool takes a payment or creates a payment link: paying an invoice happens in the SmartFlow portal.
  • The app should not act. Bank details decide where clients' money goes, so no tool changes them.
  • The app should not act. admin_send_prospect is the only tool that sends an e-mail of its own, and it cannot be aimed at an address chosen in the conversation: it sends a first message already drafted and reviewed inside the portal, to a prospect that exists in the outbound list. It is also reserved for unrestricted platform administrators, and the review account is confined to the demonstration organization.

Onboarding example

Show my project board and what is waiting on me.

View onboarding source →

Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 19, 2026. Package observed Nov 19, 2026.

View package source →

Description

From the marketplace listing

SmartFlow brings its client portal into the conversation, so the work between a service provider and its clients happens in the conversation instead of in a browser tab. Clients read their project board stage by stage, see what is waiting on them, declare it done or ask about it, read and download their documents and invoices, tell their provider an invoice was paid, read announcements, raise requests, message their provider and search their conversations, manage who in their organization has access, ask for a change to their organization's details, and export the personal data SmartFlow holds on them. Service providers run their workspace end to end: client organizations and their teams, projects, stages and tasks, client tasks and their review, documents (including a file shared in the conversation) and signature requests, draft invoices, publication, reminders and payments, recurring billing contracts with their rates, the e-mails sent and scheduled, meetings, announcements, client requests, messages and saved replies, logged time, workspace settings and the state of their integrations. SmartFlow's own administrators also triage and clean up inbound leads, outbound prospects and website reports. Every tool acts with the permissions of the signed-in SmartFlow account. Role and organization scope are checked on each call against the data itself, never taken from what the model asks for. A client never sees another organization, nor what the provider marked as internal or still draft. Tools that reach someone outside the conversation are marked as open-world: those that notify a client or a provider, e-mail an invoice, a document, an invitation or an announcement, post a test message to a team channel, or send an outbound prospect its first message; so are changes a client or a member sees (a project, its plan, logged time, a message, access) and the outbound prospect list, built from public sources. Every write that changes, replaces, cancels or removes something, notifies someone or sends an e-mail is marked destructive; only additive writes, such as creating a draft invoice or a project, are not. Before anything that notifies someone, sends an e-mail or cannot be undone, the assistant is instructed to restate what will happen and to whom, and to wait for an explicit yes. E-mails go only to the organization's billing address or its members, never to an address typed in the conversation. Invoices, documents, reminders and announcements leave through the provider's own verified sending domain; invitations come from SmartFlow's account address. Some actions deliberately stay in the portal: paying an invoice or creating a payment link, changing bank details, connecting an integration with its keys, signing a document as a client, and the settings of the SmartFlow account itself. Signing in uses your existing SmartFlow account over OAuth, with a consent screen naming the application. You can revoke that access at any time from Profile, then Security. A project board, an invoice and what is waiting on a client show as cards, and a form can ask you to choose a stage. In work chats, a service provider can also be told about client activity as it happens: a task marked done, a message, a request, a signature, a payment. The portal interface and its notifications are in French and English; the tools accept and return data in whichever language you use.

Language: English · Automatically detected from descriptions.

What changed

· 3 observations

Pricing references

Plugin name changed from “SmartFlow Portal” to “SmartFlow”. Is template instance added: “false”. App-6a9586f0e6d081918e32b97360796504 updated; open the comparison for details. Smartflow-portal updated; open the comparison for details. 14 more changes in the comparison.

View comparison →
Pricing references

Plugin name changed from “SmartFlow Portal” to “SmartFlow”. Is template instance added: “false”. App-6a9586f0e6d081918e32b97360796504 updated; open the comparison for details. Smartflow-portal updated; open the comparison for details. 13 more changes in the comparison.

View comparison →

Technical updates · 1

Package or technical metadata updated

View technical comparison →

Similar plugins

Finding similar plugins… Results will appear here automatically.

Browse plugins →

Keywords

Files & skills

File archives

Plugin package6 files · 31.1 KBBrowse files →
Skill instructions
smartflow-portal8.44 KB

View saved version →

---
name: smartflow-portal
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.
---

# SmartFlow

SmartFlow 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.

## Operating rules

- 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.
- 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.
- `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.
- 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.
- When a list returns `hasMore: true`, narrow it with a filter instead of treating the page as complete.
- 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`.
- 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.
- 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.

## Vocabulary that is easy to confuse

- **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`.
- A **client action** goes from provider to client; a **request** (`create_request`, `admin_list_requests`) goes from client to provider.
- 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.

## Client workflows

1. `list_my_actions` answers "what is waiting on me": invoices to pay, documents to sign, actions to do.
2. `get_project_board` shows one project phase by phase. `submit_my_action` declares an action done (`withdraw` takes it back).
3. `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.
4. `get_my_invoice` shows an invoice; `announce_my_invoice_payment` tells the provider it was paid by transfer.
5. `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 announce

Preview of the first 4,000 characters. Read full instructions →

smartflow-start2.6 KB

View saved version →

---
name: smartflow-start
description: Use when someone has just connected SmartFlow or asks how to get started with it. Finds out who they are, shows what matters to them right away (their project board, or what is waiting on them), then says in a few lines what they can ask and what stays in the SmartFlow portal.
---

# Getting started with SmartFlow

Run this once, at the start, when the user has just connected SmartFlow, asks "what can you do with SmartFlow?" or seems unsure where to begin. Keep it short: three steps, no lecture.

## 1. Find out who is connected

Call `get_my_account`. It says whether the account is a **client** (`staffRole: null`, with its client organizations) or a **service provider** (`workspace_staff` or `platform_admin`, with the workspaces it runs). Greet the user by name in one sentence. Never ask for an e-mail or an id: the connection already says who they are.

## 2. Show what matters now

Show something useful before explaining anything.

- **Client**: call `list_my_actions`. It shows what is waiting on them: tasks to do, invoices to pay, documents to sign. If nothing waits, say so in one line and offer to open their project with `list_my_projects`, then `get_project_board`.
- **Service provider**: call `admin_list_projects` and open the most recently active project with `get_project_board`. If there is no project yet, say so and offer to create the first one with `admin_create_project`, without creating it.

When the host shows these results as cards, do not repeat what the card already shows: add at most one sentence about the most urgent item (an overdue invoice, a task sent back with a note).

## 3. Say what they can ask, in three lines

Offer two or three examples that match their role, phrased as they would say them:

- Client: "What is still missing on my project?", "Send me the PDF of my last invoice", "Tell my provider the logo is attached."
- Service provider: "What did my clients send me this week?", "Prepare this month's invoice for my client as a draft", "Add a task for the client to send their texts by Friday."

Then say once what stays in the SmartFlow portal: paying an invoice, signing a document, bank details, connecting an integration and the SmartFlow subscription. Point to the portal for those; there is no tool for them.

## Rules that still apply

- Anything that notifies someone, sends an e-mail or cannot be undone is restated first, with who it reaches, and waits for an explicit yes.
- Read before writing: ids come from list and get tools, never from a title.
- If a tool answers with an access error, say the account does not have that role instead of retrying.

Release notes

Update to version 1.3.0. The package is now uploaded as a ZIP; its listing, test cases and release notes live in the manifest. Tools: annotations follow the current plugin guidelines. Every write that changes, cancels or removes something, notifies someone or sends an e-mail now declares destructiveHint true (42 tools changed); only additive writes keep false. New since 1.2.0: admin_pause_integration, admin_mark_invoice_unpaid and admin_delete_invoice, and the read-only get_my_profile, which lets the host tell several connected accounts apart. No tool was removed or renamed, and every argument added to an existing tool is optional. Authorization: responses from the authorization endpoint carry the iss parameter (RFC 9207), advertised in the server metadata. New in the conversation: cards (MCP Apps) for get_project_board, get_my_invoice, admin_get_invoice and list_my_actions, read-only, with an empty CSP and no payment or signing button; a getting-started skill declared as onboardingSkill; a native form that asks for the phase when admin_create_client_action gets a project without phaseId (phaseId null now means Other), with a text fallback; and MCP Events (events/list, subscribe, unsubscribe) for six client-side events, delivered by signed webhook, access checked again on every send. After the automated scan, twelve more tools declare openWorldHint true (changes a client or member sees, outbound prospects), and admin_log_time declares destructiveHint true, since passing entryId replaces an entry. Listing: the name and descriptions now describe SmartFlow alone, without naming other products or commercial terms. Listing: the paragraph on destructive tools describes the new rule, and a paragraph describes cards, the form and events. Test cases are unchanged. The review account is confined to a demonstration organization, where it can also act as a client member; platform and workspace tools refuse it on purpose.

Declared in the saved package. Remote tools may change independently.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package license
MIT
Package author
HUGO GEBEL
Keywords
See keywords
Listing translations
fr-FR
Getting started skill
./skills/smartflow-start/SKILL.md
Commerce declaration
Does not support commerceThis does not establish whether access is free or paid.
Review scenarios
5 positive · 3 negativeScenario counts, not test results.

Declared capabilities

  • Read project boards and plans
  • Track and submit client tasks
  • Manage clients and their teams
  • Build projects, stages and tasks
  • Upload documents, request signatures
  • Draft, publish and send invoices
  • Download invoice PDFs and document files
  • Set up recurring billing
  • Schedule meetings
  • Read and send messages
  • Search conversations and discuss board items
  • Publish announcements
  • Handle client requests
  • Log time
  • Review workspace settings and integrations
  • Triage leads and outbound prospects
  • Watch client activity

Package observed Nov 19, 2026.

Technical details
First seen
Sep 30, 2026 · 22:02 UTC
Last seen
Nov 19, 2026 · 12:00 UTC
Latest observed change
Oct 24, 2026 · 13:09 UTC
Collection status
Collected

plugin_asdk_app_6a9586f0e6d081918e32b97360796504

Download plugin data (JSON)

Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.