30 Claude Prompts That Build Zapier Automations

You are a senior Zapier automation architect who builds reliable lead-capture Zaps. <context> I need a complete, build-ready Zap recipe that turns every new website form submission into a CRM contact and pings my team, given as a self-contained spec I can recreate step by step in Zapier. </context> <inputs> - Form tool: [E.G. WEBFLOW, TYPEFORM, GRAVITY FORMS] - CRM: [E.G. HUBSPOT, PIPEDRIVE, SALESFORCE] - Form fields captured: [NAME, EMAIL, COMPANY, MESSAGE] - Team alert destination: [SLACK CHANNEL OR EMAIL] - Lead source tag to apply: [E.G. WEBSITE CONTACT FORM] </inputs> <task> Design the Zap end to end: trigger on a new form submission; a Formatter step to split the full name and lowercase the email; a Find-or-Create Contact action in the CRM; then a Slack or email notification. Specify each step's app, event/action, and key settings, and map every form field to its CRM destination field. </task> <constraints> - Use Find-or-Create (search first) so duplicate contacts are never created. - Name the exact trigger event and any required account connection. - Handle blank optional fields (company, phone) without breaking a step. </constraints> <format> Return the full Zap recipe as an artifact: a numbered step table (Step, App, Event/Action, Key config) plus a field-mapping table (form field to CRM field), then a short note on how to build and test it with a sample submission. </format>

You are a Zapier automation architect who specializes in paid-ads lead routing. <context> I want every Facebook or Instagram lead-ad submission logged, added to my email tool, and flagged to sales, delivered as a self-contained Zap recipe I can build step by step. </context> <inputs> - Ad account and lead form name: [ACCOUNT, FORM] - Spreadsheet for the log: [GOOGLE SHEETS TAB] - Email tool: [E.G. MAILCHIMP, ACTIVECAMPAIGN, KLAVIYO] - Tag or list for these leads: [SEGMENT NAME] - Sales alert channel: [SLACK OR SMS] </inputs> <task> Build the Zap: trigger New Lead in Facebook Lead Ads; a Formatter step to standardize phone and email format; append a row to the log sheet with a timestamp; add or update the subscriber in the email tool with the correct tag; then a Slack or SMS alert to sales with name, email, and campaign. Specify each step and map every lead-form answer to its destination. </task> <constraints> - Include a Filter so only leads with a valid email continue. - Preserve the ad and campaign name in the sheet for attribution. - Note the lead-form permissions the trigger requires. </constraints> <format> Return the Zap recipe as an artifact: a numbered step table (Step, App, Event/Action, Key config) plus a field-mapping table, then a short note on connecting the ad account and testing with a test lead. </format>

You are a Zapier automation architect who turns qualification forms into pipeline. <context> I run a Typeform to qualify prospects and want each qualified response to create a CRM deal and send a personalized welcome email, delivered as a build-ready Zap recipe. </context> <inputs> - Typeform name and key questions: [FORM, QUESTIONS] - CRM: [E.G. HUBSPOT, PIPEDRIVE] - Qualifying condition: [E.G. BUDGET OVER X, TEAM SIZE OVER N] - Deal pipeline and stage: [PIPELINE, STAGE] - Email sender and template: [FROM ADDRESS, TONE] </inputs> <task> Design the Zap: trigger on a new Typeform entry; a Filter that only continues when the qualifying condition is met; Find-or-Create the contact in the CRM; create a deal in the named pipeline and stage with the deal value from the form; then send a personalized welcome email that references their stated goal. Detail every step and map each Typeform answer to the deal and email fields. </task> <constraints> - The Filter must use the real answer field, not the whole payload. - Set deal name and amount from form fields, with a sensible default if amount is blank. - Keep the email plain-text friendly and merge in at least two answer fields. </constraints> <format> Return the Zap recipe as an artifact: a numbered step table plus a field-mapping table (Typeform answer to CRM/email field), then a short note on setting the Filter and testing an unqualified vs qualified entry. </format>

You are a Zapier automation architect who automates the booked-call workflow. <context> When someone books a call in Calendly, I want a CRM record and deal created and a reminder scheduled so no meeting is missed, delivered as a self-contained Zap recipe. </context> <inputs> - Calendly event type: [E.G. DISCOVERY CALL, DEMO] - CRM: [E.G. HUBSPOT, PIPEDRIVE, SALESFORCE] - Deal pipeline and stage: [PIPELINE, STAGE] - Reminder destination: [SLACK DM, EMAIL, OR SMS] - Reminder timing: [E.G. 1 HOUR BEFORE] </inputs> <task> Build the Zap: trigger on Invitee Created in Calendly; Find-or-Create the contact; create a deal tied to the meeting with the booked time in the notes; then a Delay Until step set to the reminder time before the call, followed by a reminder message with the invitee name, meeting link, and any answers they gave. Specify each step and map Calendly fields to their destinations. </task> <constraints> - Use Delay Until anchored to the event start minus the chosen lead time. - Capture the invitee's scheduling-question answers into the CRM notes. - Handle reschedules by noting which trigger event covers them. </constraints> <format> Return the Zap recipe as an artifact: a numbered step table plus a field-mapping table (Calendly field to CRM/reminder field), then a short note on configuring the Delay Until step and testing a booking. </format>

You are a Zapier automation architect who routes B2B ad leads into nurture. <context> I capture leads through LinkedIn Lead Gen Forms and want each one deduplicated, logged, and dropped into a nurture sequence, delivered as a build-ready Zap recipe. </context> <inputs> - LinkedIn ad form name: [FORM] - Log destination: [GOOGLE SHEETS OR AIRTABLE] - Email tool and sequence: [TOOL, SEQUENCE NAME] - Territory or owner routing rule: [E.G. BY COUNTRY OR COMPANY SIZE] - Sales notification channel: [SLACK CHANNEL] </inputs> <task> Design the Zap: trigger New Lead Gen Form Response; a Formatter to normalize company and job title casing; a Filter to drop obvious junk (free-mail-only if that matters to you); log the lead with a timestamp and source; add to the email tool and enroll in the nurture sequence; then post to the sales channel including the routing owner derived from your rule. Detail every step and field mapping. </task> <constraints> - Derive the routing owner with a Formatter or Lookup step, not by hand. - Only enroll in the sequence after a successful log and dedupe. - Name the LinkedIn connection scope the trigger needs. </constraints> <format> Return the Zap recipe as an artifact: a numbered step table plus a field-mapping table (LinkedIn field to log/email field), then a short note on the routing logic and how to test one lead. </format>

You are a Zapier automation architect who builds clean revenue notifications. <context> I want a Slack alert every time we take a payment in Stripe, formatted so the team can read it at a glance, delivered as a self-contained Zap recipe I can build step by step. </context> <inputs> - Stripe event to watch: [E.G. NEW CHARGE, NEW PAYMENT, NEW SUBSCRIPTION] - Slack channel: [CHANNEL NAME] - Details to show: [AMOUNT, CUSTOMER, PRODUCT, PLAN] - Minimum amount to alert on: [E.G. NONE OR OVER X] - Currency handling: [SINGLE OR MULTI-CURRENCY] </inputs> <task> Build the Zap: trigger on the chosen Stripe event; a Formatter to convert the amount from cents to a currency-formatted string; an optional Filter for a minimum amount; then a formatted Slack message using blocks or emoji showing customer, amount, product, and a link to the payment in Stripe. Specify each step and map every Stripe field into the message. </task> <constraints> - Convert amounts from cents and format the currency correctly. - Keep the Slack message scannable: one bold line plus supporting details. - Include a direct link to the charge in the Stripe dashboard. </constraints> <format> Return the Zap recipe as an artifact: a numbered step table plus a field-mapping table (Stripe field to message field), then a short note on the amount Formatter and testing with a Stripe test event. </format>

You are a Zapier automation architect who builds priority-inbox notifications. <context> I want to be alerted instantly when an email from a key sender or with an urgent keyword hits my inbox, delivered as a build-ready Zap recipe. </context> <inputs> - Mailbox: [GMAIL OR OUTLOOK] - VIP senders or domains: [ADDRESSES OR DOMAINS] - Urgent keywords: [E.G. URGENT, DOWN, CANCEL] - Alert channels: [SLACK DM, SMS, OR BOTH] - Quiet hours to skip SMS: [E.G. 10PM-7AM OR NONE] </inputs> <task> Design the Zap: trigger on a new email (or new labeled email); a Filter that continues only when the sender is a VIP OR the subject/body contains an urgent keyword; a Formatter to trim the body to a preview snippet; then a Slack DM and, outside quiet hours, an SMS with sender, subject, and snippet. Detail every step and map the email fields into each alert. </task> <constraints> - The Filter must combine sender AND keyword logic correctly (OR within, AND across as needed). - Truncate the body to a short preview to avoid huge messages. - Show how to skip SMS during quiet hours with a time-based condition. </constraints> <format> Return the Zap recipe as an artifact: a numbered step table plus a field-mapping table (email field to alert field), then a short note on writing the Filter logic and testing a VIP vs non-VIP email. </format>

You are a Zapier automation architect who automates meeting prep. <context> Before each meeting I want a Slack DM with the details and any prep notes, delivered as a self-contained Zap recipe I can build step by step. </context> <inputs> - Calendar: [GOOGLE CALENDAR OR OUTLOOK] - Which events to include: [ALL, OR ONLY WITH GUESTS, OR A KEYWORD] - Lead time: [E.G. 15 MINUTES BEFORE] - Slack recipient: [ME OR A CHANNEL] - Extra info to pull: [MEET LINK, ATTENDEES, LOCATION, DESCRIPTION] </inputs> <task> Build the Zap: trigger on Event Start (with the chosen lead time) in the calendar; a Filter to include only the events you care about; a Formatter to build a tidy attendee list and extract the video link from the description; then a Slack message with title, time, attendees, join link, and any agenda text. Specify every step and map calendar fields to the message. </task> <constraints> - Use the Event Start trigger with the lead time, not a scheduled poll. - Extract the meeting link reliably even if it sits inside the description. - Skip all-day and declined events with the Filter. </constraints> <format> Return the Zap recipe as an artifact: a numbered step table plus a field-mapping table (calendar field to message field), then a short note on the Event Start timing and testing with a near-future event. </format>

You are a Zapier automation architect who builds support-escalation Zaps. <context> When a high-priority or angry support ticket comes in, I want it escalated to the right people fast, delivered as a build-ready Zap recipe. </context> <inputs> - Helpdesk: [E.G. ZENDESK, INTERCOM, FRESHDESK] - Escalation triggers: [PRIORITY = URGENT, VIP CUSTOMER, OR NEGATIVE SENTIMENT WORDS] - Escalation channel: [SLACK CHANNEL AND/OR ON-CALL SMS] - On-call owner rule: [E.G. BY PRODUCT AREA OR ROUND-ROBIN] - SLA clock to mention: [E.G. RESPOND WITHIN 30 MIN] </inputs> <task> Design the Zap: trigger on a new or updated ticket; a Filter that continues only when an escalation condition is met; a Formatter to detect the product area and pick the on-call owner; then a Slack alert that @mentions the owner with ticket subject, customer, priority, and a direct link, plus an optional SMS. Detail each step and map every ticket field into the alert. </task> <constraints> - Combine priority, VIP, and keyword conditions in one clear Filter. - Resolve the owner with a lookup/Formatter step, never hardcoded per case. - Include the ticket URL and state the SLA in the message. </constraints> <format> Return the Zap recipe as an artifact: a numbered step table plus a field-mapping table (ticket field to alert field), then a short note on the escalation Filter and testing an urgent vs normal ticket. </format>

You are a Zapier automation architect who designs multi-branch notification Zaps. <context> When a new request comes in, different teams should be notified based on its type, delivered as a self-contained Zap recipe using Zapier Paths. </context> <inputs> - Intake source: [E.G. FORM, EMAIL, OR TICKET] - Category field that decides routing: [E.G. REQUEST TYPE] - Branches and destinations: [E.G. SALES to CHANNEL A, SUPPORT to CHANNEL B, BILLING to CHANNEL C] - Fallback for unknown types: [DEFAULT CHANNEL] - Details to include in each alert: [FIELDS] </inputs> <task> Build the Zap: trigger on the new intake item; a Formatter to normalize the category value; then Paths, one per branch, each with its own rule and a tailored Slack or email notification to that team; and a final fallback path for anything unmatched. Specify the trigger, each Path's condition, and the message for every branch, and map intake fields into each alert. </task> <constraints> - Each Path condition must be mutually exclusive and cover the fallback case. - Normalize the category (trim, lowercase) before the Path rules read it. - Keep every branch message consistent in structure but team-specific. </constraints> <format> Return the Zap recipe as an artifact: a numbered step table showing the trigger and each Path (condition plus action) and a field-mapping table, then a short note on ordering Paths and testing each branch. </format>

You are a Zapier automation architect who builds dependable data-sync Zaps. <context> I want each new row in a Google Sheet to create or update a matching record in Airtable so the two stay aligned, delivered as a build-ready Zap recipe. </context> <inputs> - Source sheet and tab: [SHEET, TAB] - Airtable base and table: [BASE, TABLE] - Unique key to match on: [E.G. EMAIL OR ORDER ID] - Columns to sync: [LIST OF FIELDS] - Type conversions needed: [E.G. DATES, NUMBERS, CHECKBOXES] </inputs> <task> Design the Zap: trigger on a new or updated spreadsheet row; a Formatter to coerce dates and numbers into the formats Airtable expects; a Find Record step in Airtable on the unique key; then Create-or-Update the Airtable record with the mapped columns. Specify every step and provide a full column-to-field mapping table. </task> <constraints> - Match on the unique key so rows update rather than duplicate. - Convert data types explicitly (dates, numbers, single vs multi-select). - Skip empty rows with a Filter so blank triggers do nothing. </constraints> <format> Return the Zap recipe as an artifact: a numbered step table plus a field-mapping table (sheet column to Airtable field with its type), then a short note on the match key and testing a new vs edited row. </format>

You are a Zapier automation architect who keeps store and email data in sync. <context> I want new Shopify customers added to the right Mailchimp audience with tags reflecting their behavior, delivered as a self-contained Zap recipe. </context> <inputs> - Shopify store: [STORE NAME] - Mailchimp audience: [AUDIENCE NAME] - Tags to apply: [E.G. CUSTOMER, FIRST-ORDER, ACCEPTS-MARKETING] - Merge fields to fill: [FIRST NAME, LAST NAME, CITY, TOTAL SPENT] - Marketing-consent rule: [ONLY IF OPTED IN] </inputs> <task> Build the Zap: trigger on a new Shopify customer (or new paid order); a Filter that continues only when the customer accepts marketing; a Formatter to split names and format total-spent; then Add/Update Subscriber in Mailchimp with merge fields and tags. Specify each step and map every Shopify field to its Mailchimp merge field or tag. </task> <constraints> - Respect marketing consent with a Filter before subscribing anyone. - Use Add/Update so returning customers are not duplicated. - Map tags precisely and format numeric fields for Mailchimp. </constraints> <format> Return the Zap recipe as an artifact: a numbered step table plus a field-mapping table (Shopify field to Mailchimp merge field/tag), then a short note on the consent Filter and testing with a sample customer. </format>

You are a Zapier automation architect who mirrors pipeline changes into a reporting base. <context> When a deal changes stage in my CRM, I want the matching Airtable row updated so my ops base always reflects the pipeline, delivered as a build-ready Zap recipe. </context> <inputs> - CRM: [E.G. HUBSPOT, PIPEDRIVE, SALESFORCE] - Airtable base and table: [BASE, TABLE] - Deal unique key: [E.G. DEAL ID] - Fields to sync: [STAGE, AMOUNT, OWNER, CLOSE DATE] - Stages that should also alert: [E.G. WON, LOST] </inputs> <task> Design the Zap: trigger on Deal Stage Changed (or Updated Deal); a Find Record in Airtable on the deal key; a Formatter to stamp a stage-changed timestamp and format the amount; Update the Airtable record; then a conditional Slack alert only for the milestone stages you named. Specify each step and map every CRM field to its Airtable field. </task> <constraints> - Match on the deal ID so the right row is updated every time. - Only alert on the milestone stages, using a Filter or Path. - Record when the stage changed, not just the new stage. </constraints> <format> Return the Zap recipe as an artifact: a numbered step table plus a field-mapping table (CRM field to Airtable field), then a short note on the match key and testing a stage move to Won. </format>

You are a Zapier automation architect who automates bookkeeping handoffs. <context> When an invoice is created in my billing tool, I want it recorded in my accounting software and logged for the finance team, delivered as a self-contained Zap recipe. </context> <inputs> - Billing source: [E.G. STRIPE, PAYPAL, INVOICE TOOL] - Accounting tool: [E.G. QUICKBOOKS, XERO] - Customer match key: [EMAIL OR CUSTOMER ID] - Fields to record: [AMOUNT, TAX, LINE ITEMS, DUE DATE] - Finance log: [GOOGLE SHEETS TAB] </inputs> <task> Build the Zap: trigger on a new invoice; a Formatter to convert amounts and dates to the accounting tool's expected format; Find-or-Create the customer in the accounting tool; create the invoice/sales receipt with line items and tax; then append a row to the finance log. Specify each step and map every billing field to its accounting-tool field. </task> <constraints> - Format currency amounts and dates exactly as the accounting tool requires. - Find-or-Create the customer so duplicates are avoided. - Preserve line-item detail and tax rather than a single lump total. </constraints> <format> Return the Zap recipe as an artifact: a numbered step table plus a field-mapping table (billing field to accounting field), then a short note on line-item handling and testing a sample invoice. </format>

You are a Zapier automation architect who keeps address books and mailing lists aligned. <context> When a contact is created in my CRM, I want it added to Google Contacts and my newsletter list so nothing lives in one place only, delivered as a build-ready Zap recipe. </context> <inputs> - CRM: [E.G. HUBSPOT, PIPEDRIVE] - Google Contacts label: [E.G. CUSTOMERS] - Newsletter tool and list: [TOOL, LIST] - Fields to sync: [NAME, EMAIL, PHONE, COMPANY] - Consent rule for the newsletter: [ONLY IF OPTED IN] </inputs> <task> Design the Zap: trigger on a new CRM contact; a Formatter to normalize the phone number to E.164 and split the name; Create-or-Update a Google Contact with the right label; a Filter for newsletter consent; then Add/Update the subscriber in the newsletter tool. Specify each step and map every CRM field to both destinations. </task> <constraints> - Normalize phone numbers to E.164 for clean Google Contacts entries. - Only add to the newsletter when consent is present. - Use Create-or-Update everywhere so records stay unique. </constraints> <format> Return the Zap recipe as an artifact: a numbered step table plus a field-mapping table (CRM field to Google Contacts and newsletter fields), then a short note on the phone Formatter and testing a new contact. </format>