Inbox & email · Workflow template

Flag attachments; reply DRIVE to save to Drive

When a PDF or Word document arrives, get a flag email about it. Reply DRIVE and the attachment is saved to your Google Drive with a confirmation; ignore the flag and nothing happens. No AI.

Gmail Outlook Google Drive

The workflow at a glance

Trigger
New email
Tool
Run Python
Branch
Route
Action
Save attachment
Branch
Saved ok
Tool
Run Python
Action
Send email
Action
Send email
Branch
Command missing ref
Action
Send email
Branch
Has attachment
Tool
List attachments
Branch
Is document
Tool
Run Python
Action
Send email

How this workflow works, step by step

  1. 1 Trigger New email

    The workflow starts when Gmail or Outlook signals "new email". Carly is listening continuously, so the run begins within seconds of the event.

  2. 2 Tool Run Python

    Carly pulls live data from the connected tool — "Run Python." Whatever's needed for the next step is fetched fresh, not cached.

  3. 3 Branch Route

    The flow splits on "Route." Different inputs follow different paths through the rest of the workflow.

  4. 4 Action Save attachment

    Finally Carly takes action in Google Drive: save attachment. This is the thing that actually moves the world.

  5. 5 Branch Saved ok

    The flow splits on "Saved ok." Different inputs follow different paths through the rest of the workflow.

  6. 6 Tool Run Python

    Carly pulls live data from the connected tool — "Run Python." Whatever's needed for the next step is fetched fresh, not cached.

  7. 7 Action Send email

    Finally Carly takes action in Gmail or Outlook: send email. This is the thing that actually moves the world.

  8. 8 Action Send email

    Finally Carly takes action in Gmail or Outlook: send email. This is the thing that actually moves the world.

  9. 9 Branch Command missing ref

    The flow splits on "Command missing ref." Different inputs follow different paths through the rest of the workflow.

  10. 10 Action Send email

    Finally Carly takes action in Gmail or Outlook: send email. This is the thing that actually moves the world.

  11. 11 Branch Has attachment

    The flow splits on "Has attachment." Different inputs follow different paths through the rest of the workflow.

  12. 12 Tool List attachments

    Carly pulls live data from Gmail or Outlook — "List attachments." Whatever's needed for the next step is fetched fresh, not cached.

  13. 13 Branch Is document

    The flow splits on "Is document." Different inputs follow different paths through the rest of the workflow.

  14. 14 Tool Run Python

    Carly pulls live data from the connected tool — "Run Python." Whatever's needed for the next step is fetched fresh, not cached.

  15. 15 Action Send email

    Finally Carly takes action in Gmail or Outlook: send email. This is the thing that actually moves the world.

When to use this template

  • You want this work to happen consistently without anyone remembering to do it.
  • You're already using Gmail and Outlook, and the manual version of this is eating real minutes a week.
  • You want a visible canvas you can audit and edit — not a black-box agent doing things you can't see.

When not to use it

  • This task only happens once or twice a month — the setup cost won't pay back.
  • The decision in the middle of the flow needs human judgment every single time, not just on edge cases.
  • Your stack doesn't include any of the apps above and you don't want to wire a generic HTTP step.

Build it in 10 minutes — copy this prompt

Paste this in an email to and Carly will build the workflow for you.

Hey Carly — set up the "Flag attachments; reply DRIVE to save to Drive" template for me and turn it on once it's working. If you need any details from me (like which sender, folder, or channel), just ask. Thanks!

Apps you'll connect

Carly authenticates these for you over OAuth when she sets up the workflow.

Gmail
Outlook
Google Drive

Questions teams ask before building this

How long does this workflow take to set up?

Most teams have "Flag attachments; reply DRIVE to save to Drive" running in under 10 minutes. Copy the prompt on this page into an email to carly@usecarly.com and Carly wires the workflow together for you, including authenticating Gmail.

Can I edit this template after Carly builds it?

Yes. Every workflow lives on the Carly canvas where you can rename steps, change conditions, swap LLM models, add filters, and re-route branches. Templates are starting points, not locked recipes.

What if I use a different tool than the ones in this template?

Carly connects to thousands of apps, and a generic HTTP node covers anything without a ready-made connector. Tell Carly your stack when you send the prompt and she'll pick the right connectors.

Does this run automatically once it's built?

Yes. The trigger at the start of the workflow fires automatically — on a schedule, on an inbound email, on a webhook, on a calendar event, whatever this template specifies. Carly handles the listening; you only step in when a step is gated on you.

Does this workflow cost anything to run?

This template has no AI step, so it runs free — no subscription required. Carly only charges when a workflow step calls an AI model, and this one doesn't. Build it, set it on whatever trigger you like, and it keeps running at no cost.

Ready to run Flag attachments; reply DRIVE to save to Drive?

Carly will build it for you and you'll be up and running in 10 minutes.

Build it in Carly