The result to aim for
Brevo salesmen ask a Dust agent: "the top 3 e-commerce customers to name"; The agent questions the CRM mirror (sector, size, usage) instead of 10–15 minutes of manual search.
What was done
Same page Dust Brevo. Workflow 1 "Customer Reference Finder". Before: 10–15 minutes of CRM research, tribal knowledge. After: request in natural language, structured recommendations (deadline of implementation, results, case of use). Quote The Goupil: "That workflow alone changed how reps prepare for calls. Distinct from the e-mail generation.
Before you start
Tool cited by the source: Dust (MCP Supabase). Fill in the bracketed items: [secteur, taille], [coller]. Strip confidential data that is not needed and check your tool’s access terms. Features and plans can change.
The method, in three steps.
Gather the context
Spot the bracketed items in the prompt (
[secteur, taille],[coller]) and prepare what they ask for.Adapt the prompt
Copy the prompt below, replace the bracketed items, then paste it into the AI assistant you use. The cited tool (Dust (MCP Supabase)) is not necessarily available to the public..
Reread before using
Reread the result, correct it if needed and keep the final decision. Caveats are detailed below.
Your starting point.
Replace the bracketed items, then adapt the proposal to your situation. This prompt is written by the iadujour desk It is not a quotation from the source.
Prospect: [secteur, taille]. Extract CRM (anonymized, clients who agreed to be cited): [coller]. Top 3 references, why, angle. If no match: "no validated reference".
What deserves your attention
Proof level: Statement by the tool’s publisher. Source checked on 10 November 2026. Use described by the source, not tested by the desk. Original summary written by iadujour.fr: figures and claims are the source’s; the prompt is a desk proposal, not a quotation.
Useful skills
Official skills on the same task, paired by the desk: they are not part of the described case.
- Good practices Postgres (Supabase)Supabase · Collects the best Postgres practices maintained by Supabase, valid for a Postgres hosted anywhere, not just on Supabase.
- Develop with SupabaseSupabase · This skill applies to any Supabase task: base, Auth, Edge Functions, Realtime, Storage, vectors, cron, file, client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro or Remix, troubleshooting (session, JWT, cookies, getSession, getUser, getClaims, RLS), CLI or MCP server, schemas, migrations, audits, Postgres extensions, and debugging ( HTTP or Postgres errors, RLS, schema cache, timesouts, Logs Explorer / ClickHouse logs).
- Optimize Postgres according to Supabase practices, in Build Web AppsOpenAI · Collect, in the OpenAI Build Web Apps plugin, Postgres optimization practices maintained by Supabase.
- Configuring Supabase auth emailsPostHog · Connect a Supabase project so that its auth emails send via PostHog email templates via the Supabase Send Crochet Email, in an order that never breaks an entry.
Comments.
A field note, a question, a precision on this use case? Comments are reviewed before publication.
Published comments
Loading comments…
Leave a comment
Moderation charter. Every comment is reviewed before publication. We refuse hate speech, insulting or discriminatory language, advertising, spam and promotional links, off-topic posts and other people’s personal data.