A read-only agent answers stock and price questions from a sheet, at 3 credits each.
The prompt · from the source
You are a read-only inventory assistant for a small shop. Always call the get_inventory_by_product tool before answering a stock or price question. Answer only from the tool result. If the user did not name a product, ask which product they mean. If the tool returns nothing, say you have no record of that product and do not guess. If Stock is 0, say it is out of stock. Prices are USD each. If the tool fails or is unavailable, say the stock cannot be verified right now. You cannot reserve, order, or change stock; say so if asked. Keep answers to one or two sentences.
A solo creator's invoicing fell from about an hour per client to seconds, saving 15 or more hours a month.
Try it · based on the source's workflow
When I mark a project ready to bill in [system], build its invoice from this template: [link]. Pull the client, project, and amount from [source]. Draft a short personal email with the invoice attached and show it to me before sending. After I approve, send it, log it in [CRM or sheet], and notify me. Run this only on [day].
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
An agent writes each product newsletter in 9-13 minutes, down from up to 2 hours, and the store counted 43 extra purchases in a month.
Try it · based on the source's workflow
For each row in [sheet] with a topic and product focus, find matching products in [store] and write a newsletter draft in [document]. Use only real product names, prices, and links from the store. Keep the tone of [brand notes]. Stop at the draft. I check quality and tone before any send.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
An agent drafts product advice replies with live stock data, and time per email fell from about 12.5 minutes to 3.25.
Try it · based on the source's workflow
Watch [inbox] for customer emails. Classify each as a product or policy question, or a private or order question. For private or order questions, send only the holding reply and route to a person. For product questions, check live stock and policy pages for [store], then draft a reply with the product links. Save drafts only. Do not send. I review and send each draft.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
A Chicago lunch spot runs bookings, reviews, and confirmations for $62 a month.
Try it · based on the source's workflow
Run the evening admin for [restaurant name]. Read new booking requests from [message channels]. Take the name, party size, and date. Check open slots in [availability sheet]. Reply with a confirmation or other times. When a new Google review arrives, draft a reply that names what the guest mentioned. Show me the draft. Send it only after I approve it. Each day at [time], send a text confirmation to tomorrow's bookings with the time and a reschedule link. Show me a summary each night.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
A marketing firm's Make and Claude workflow cut a 16-hour blog job to 6 hours.
Try it · based on the source's workflow
Build a blog drafting workflow for [firm name] in Make. Trigger: a new row in [Google Sheet] with a topic, a keyword target, and a source brief in [Google Doc]. Send the brief, our brand voice notes [paste], and the keyword target to Claude and draft a post of about [word count] words. Rules: no cliche phrases from this list [list], keep adjectives low, and match the structure of this sample post [link]. Save the draft to [Google Doc folder] and post the link in [Slack channel] for my review. Do not publish anything. I approve every post before it goes live.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
A free workflow reposts to three platforms. Posting fell from 45 minutes a day to 10.
Try it · based on the source's workflow
Set up a workflow in [automation tool] that takes each new post from [source] and reposts it to [platforms] at the times I set. Keep the text and link the same as the source post. Send me a daily log that lists each post and where it went. Stop and show me any post that fails. I will write all replies to people myself. Do not write or send replies.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
One commenter runs lead checks, onboarding, and basic service replies with Make and AI.
Try it · based on the source's workflow
For each new lead from [source]: check the lead against [my criteria] and score it. If it passes, send the onboarding steps in [tool]: [list steps]. Answer basic service questions from [FAQ document] only. If a question is not in the document, draft a reply and show me before it sends. Log every lead and its score in [sheet].
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
The client asked for an AI agent; a four-day Make scenario connecting three tools saved 15 hours a week instead, and they still paid.
Try it · based on the source's workflow
Before building anything, map my customer onboarding flow step by step: every tool, every handoff, and every place the same information gets typed twice. Then design the simplest automation that connects those tools, using [Make or Zapier] scenarios where plain connections are enough and AI only where a step needs judgment. Show me the map and the plan before you build, and list the hours each step costs us today.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
Three Make scenarios turn approved Monday purchase orders into Xero POs, invoices and bills, with no manual entry in Xero.
Try it · based on the source's workflow
Build a sync between [Monday.com] and [Xero] with Make. When a purchase order on [board] is marked [ready or approved], create the purchase order in Xero with all line items, find or create the supplier, save the PDF back to the Monday item, and create the matching bill. Do the same for client invoices, attach the PDF, and email it to the client only after I approve the first few. If any step fails, flag the Monday item [Needs Attention] with a comment saying exactly what broke. Show me three test orders end to end before it runs on live data.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.