ChatGPT Workflow Templates: 9 Worth Copying
“Template” means two different things in ChatGPT, and searching for one gets you the other. There is the official sense, where OpenAI’s plugin directory bundles apps, skills, and app templates into installable packages. And there is the everyday sense: a reusable structure you paste in to run the same job the same way every time.
This page is about the second, because it is what people actually want and what nothing ships by default. Below are nine structures worth keeping, plus the honest limit they all run into.
What makes a template rather than a prompt
A prompt gets you one good answer. A template gets you the same quality on the twentieth run, when you are tired and the input is messier than the example. Three things separate them:
- A fixed output shape. State the format explicitly, or you will get prose one day and a table the next, and you cannot build a habit on that.
- A stated failure mode. Tell it what to do with missing information. “If the source does not say, write UNKNOWN rather than inferring” prevents the confident guess that quietly poisons the output.
- The context named up front. Who this is for and what happens next. The same summary written for you and written for a client are different documents.
Nine templates
1. Thread to decision log. Read this thread. Return: decisions made, who owns each, open questions, and what is blocked. Anything not explicitly stated goes under “not addressed” rather than being inferred.
2. Meeting transcript to follow-up. From this transcript, draft the follow-up email: what we agreed, what I owe them with dates, what they owe me with dates. Keep it under 200 words and match the tone of the transcript.
3. Inbox triage pass. Sort these messages into: needs a reply from me today, needs a reply this week, needs no reply, and needs someone else. For the first group only, draft a one-paragraph response.
4. The weekly rollup. Here are last week’s figures against the previous week. Report only what changed by more than 10%, with the likely cause where the data supports one. Do not editorialize on things that held steady.
5. Document to brief. Reduce this to one page for someone who will not read the original: what it is asking for, what it costs, what the risks are, and the decision required. Write UNKNOWN where the document is silent.
6. Pre-call prep. Given this account history and recent email, produce: where we left off, what they care about, what has changed since, and three questions worth asking.
7. Objection response. Draft three replies to this objection, each at a different level of concession, and mark which one I should not send unless they push twice.
8. Content repurpose. Turn this into a short post, keeping the specific numbers and dropping the setup. No introductory sentence about why the topic matters.
9. Cleanup and normalize. Standardize this list: consistent capitalization, deduplicated, missing fields marked rather than guessed. Return only the rows you changed, with what changed.
Making them stick
Templates decay when they live in a note file you have to go find. Three ways to keep them close:
- A project with instructions attached, so the standing context is loaded before you type anything.
- Custom instructions for the two or three rules you want on every conversation, like the “write UNKNOWN” habit above.
- A scheduled task for anything genuinely recurring, so the weekly rollup runs on Monday whether or not you remember it.
The step none of these covers
Every template above has the same shape: you bring the material, it produces the output. That is the ceiling, and it is worth being clear-eyed about.
The unattended-work gap closed when ChatGPT and Claude Cowork added scheduled runs. Their standard schedulers still start from the clock, not arbitrary events in connected apps; API-triggered ChatGPT Workspace Agents require an external event detector and caller.
Which means template 3, the inbox triage pass, only runs when you paste the messages in. Template 6, pre-call prep, only helps if you remember to run it before the call. The template makes the output consistent. It does not make the job happen.
For a lot of work that is fine. For anything where the timing is the point, the missing piece is not a better prompt.
Templates that run themselves
The version of this that closes the gap is a workflow with a trigger on the front: the same repeatable structure, started by the event rather than by you.
Carly works that way, and the workflow template library is the starting set. The difference in practice:
- The triage template becomes mail being sorted and the routine replies answered as it arrives, so what is left in the inbox is what needs you.
- The pre-call prep template becomes a brief that is already waiting before every meeting, assembled from the account history and recent email.
- The follow-up template becomes notes written, records updated, and the follow-up sent, in the few minutes after the meeting ends.
You describe the job in plain English and Carly asks the follow-up questions rather than handing you a canvas to draw on. It connects natively to around 260 apps, plus anything else with a public API through your own key on carlyassistant.com/integrations. Zapier-style workflow steps are free, and AI agents start at $35/month.
FAQ
Does ChatGPT have built-in workflow templates? Not in the reusable-structure sense. OpenAI’s plugin directory includes app templates as part of installable packages, which is a developer-facing idea. For everyday recurring work you build your own structures and store them in projects, custom instructions, or scheduled tasks.
What is the difference between a ChatGPT template and a custom GPT? A template is text you reuse; a custom GPT packages instructions, and optionally files and tools, into something you can open directly and share. If a template is earning its keep and other people need it, that is the point to turn it into a GPT. Neither one runs on its own.
Can a ChatGPT workflow template run automatically? Only on a schedule, through scheduled tasks, and those poll at most once an hour rather than reacting to events. Nothing starts because an email landed or a record changed. For templates that need to fire on an event, you need a platform built around triggers, such as Carly.
Why do my templates work at first and then drift? Usually because the failure mode was never stated. A template that does not say what to do with missing information will fill the gap with something plausible, and plausible-but-wrong is hard to spot at a glance. Adding an explicit instruction to mark unknowns rather than infer them fixes most of it.
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
