Workflows
A workflow runs fixed instructions on a model automatically, on a schedule you set. Use it for the reports, digests and checks you would otherwise ask for by hand every week.
Some requests come back like clockwork: the Monday competitor round-up, the morning sales numbers, the list of overdue invoices. A workflow does that work for you. You set a schedule, choose a model and write the instructions once. StickyPrompts runs it on time, can use your connected integrations along the way, and keeps a history of every run.
Your workflows
Workflows in the left sidebar lists every workflow with its model, a plain-language summary of its schedule and an on/off toggle.
Create a workflow
- Choose New workflow
On the Workflows page, select New workflow. Give it a name and a short description that says what it delivers, for example Monday competitor digest - Every Monday: what changed at our top five competitors last week.
- Set the schedule
Under Set the schedule, pick a Frequency: Hourly, Daily, Weekly, Monthly or Custom Cron. Then set the day, the Time and the Timezone. A summary line underneath confirms it in plain words, such as Runs every Mon at 09:00 (Europe/Budapest).
Use Custom Cron only when the presets cannot express the schedule, such as “weekdays at 07:30”.
- Choose the AI model
Under Choose the AI model, pick the model that powers this workflow. A digest that has to reason across many sources deserves a strong model; a short status check can use a faster one.
- Write the instructions
Under Write the instructions, tell the model what to do each time the workflow runs. Start from a template if one is close - Sales report email, Weekly summary digest, Inventory alert, Customer churn digest or Invoice reminders - and adapt it.
Write the instructions as if nobody will be there to answer questions: say what data to use, what to produce, in what format, and what to do if something is missing.
- Check the integrations and MCP tools
The model uses your connected integrations and remote MCP tools automatically when the workflow runs - a database to query, a CRM to read, the email connection to send the result. Integrations / MCP Tools shows what is available to it. See Integrations.
- Save, then Run now
Select Save. Then select Run now to test it immediately instead of waiting for the schedule, and check the result in History.
No action blocks: just say what should happen
There is no “send email” block, no “make PDF” block and no flowchart to wire up. A workflow is one set of instructions, and the model does every step with the same tools it has in chat. So you write the outcome:
Pull every open deal from Pipedrive and group them by stage with a total
per stage. Turn that into a one-page PDF pipeline brief: a headline number,
a table of deals, and the three deals most at risk with one line on why.
Email the PDF to our CFO as an attachment, with a three-line summary in
the email body.Notice what is missing: an email address. StickyPrompts can see who is in your workspace, so “our CFO”, “Sarah” or “the sales team” is enough. When this ran, the model found Sarah Kim through the Finance team’s description, made the PDF, and sent it:
What you can ask a workflow to do, in plain words:
| Ask for | What happens |
|---|---|
| “Email it to Sarah” / “send it to the CFO” | The recipient is looked up among your teammates. |
| “As a PDF” / “as a Word document” | The file is created and attached to the email. |
| “From the retail database” / “from Pipedrive” | Your connected integrations are queried. |
| “Using the Help Center knowledge base” | Your documents are searched and cited. |
| “With a banner image for the newsletter” | StickyPrompts’ image generation is called, like in chat. |
Enable, pause and run on demand
- The Enabled toggle (also on each row of the list) turns the schedule on or off. Paused workflows keep their schedule but never run, so you can pause over a holiday and switch back on without re-entering anything.
- Run now starts a run straight away. It is the quickest way to test a change to the instructions.
- The header shows Total runs and Success rate (last 30) so you can see at a glance whether a workflow is healthy.
History and results
Select History to see every run: its status, how it was triggered and when it ran. Expand View result to read exactly what the model produced that time.
Examples
Monday competitor digest
Schedule: Weekly, Monday, 09:00, Europe/Budapest. Model: Claude Opus 5.5.
Write the weekly competitor digest for the Northwind Analytics team.
For each of our top five competitors, summarise what changed last week:
pricing, new features, notable announcements. One short paragraph each.
Finish with "What this means for us": at most three bullet points.
If nothing changed for a competitor, say so in one line.
Keep the whole digest under 400 words.Daily store pulse
A morning summary of yesterday across all 12 Northwind stores. Schedule: Daily, at the time the team starts work. Model: Claude Opus 5.5. Integrations: the Northwind Retail DB PostgreSQL connection (read only), plus the email connection if the pulse should land in inboxes.
Using the Northwind Retail database, summarise yesterday's trading
for each of our 12 stores: revenue, orders and average order value,
compared with the same weekday last week.
Start with a three-line overview for the whole chain.
Then list any store more than 10% below last week, with one likely reason
from the data.
Email the summary to the store operations team.Tips
- One outcome per workflow. A digest and an alert are two workflows. Each is easier to read and to fix.
- Connect with the least access needed. A reporting workflow only needs a Read only database connection.
- Say what “nothing to report” looks like. Otherwise the model may pad a quiet week.
- Check the timezone. A 09:00 digest in the wrong timezone arrives in the middle of the night.