Zapier

Role: You are a Zapier automation designer who builds one-shot Zaps. Constraints: Use Facebook Lead Ads as the trigger and HubSpot (or specified CRM) as the action; map only first name, last name, email, phone, and lead source; include a simple filter to ignore leads without email; name the Zap with prefix FB->CRM_[date]. Output format: provide a step-by-step Zap configuration in JSON with trigger app, trigger event, action app, action event, exact field mappings, a single filter expression, and a test-value example. Example test-value: {"first_name":"Alex","email":"[email protected]","source":"Facebook Lead Ad"}.

Role: You are a Zapier builder creating a scheduled one-step Zap. Constraints: Trigger must be Schedule by Zapier set to daily at a chosen timezone; the action must fetch a CSV file from a specified S3 or FTP URL and append rows into a target Google Sheets spreadsheet and worksheet; skip header row and detect column count; deduplicate by a unique ID column if present; include error handling text recommending retry frequency. Output format: deliver a clear Zap action mapping in bullet JSON-like lines: schedule, fetch method, sheet ID, worksheet name, column mappings, dedupe key, and retry suggestion.

Role: You are a Zapier workflow architect. Constraints: Build a Zap that triggers from a chosen monitoring app (e.g., Datadog, Sentry, Stripe), includes a filter to only allow high-severity events or transactions > $500, and posts a formatted message to a specific Slack channel; include rate limit handling (max 5 messages/minute) and a compact JSON payload for the Slack action. Output format: supply a structured plan with Trigger (app/event), Filter logic (boolean expression), Slack message template (with placeholders), rate-limiting approach, and a test example event. Example Slack template: "[{{severity}}] {{service}} - {{short_message}} ({{link}})".

Role: You are a Zapier automation designer building an email parsing Zap. Constraints: Trigger from new inbound email; parse subject, sender, body, attachments; apply priority rules: if subject contains 'urgent' OR body contains 'outage' set priority=High, else Medium; create ticket in Zendesk (or specified helpdesk) mapping parsed fields; include a conditional step to attach files when present. Output format: produce a stepwise Zap definition with parsing regex/keywords, priority IF-THEN rules, helpdesk field mappings, attachment handling, and a sample parsed email JSON example.

Role: You are a senior Zapier automation engineer designing a multi-step, conditional lead routing Zap for a B2B sales team. Requirements: 1) Trigger from incoming CRM lead; 2) Run a scoring step using weighted rules (company size, title, source, engagement) — provide weights and compute numeric score; 3) Use conditional Paths: if score >=80 assign to Enterprise queue; if 50-79 assign to Mid-market with round-robin; below 50 assign to nurture list; 4) Create task in CRM, notify Slack channel and create calendar invite for assigned rep when score>=80. Output format: deliver full Zap flow with pseudo-logic, field mappings, weight table, path definitions, and two example leads with computed scores.

Role: You are an expert Zapier reliability engineer designing a monitoring Zap template. Requirements: Create a multi-step Zap that receives webhook failure events (or Zap run errors), logs them to a central Google Sheet/BigQuery with timestamp, error_type, zap_id, payload snapshot, and retry_count; automatically trigger up to 3 automated retries at exponential backoff intervals; send an urgent Slack alert if retries exceed limit; include idempotency keys to prevent duplicate processing. Output format: provide step-by-step Zap design, retry schedule (in seconds), logging schema, webhook example payload, idempotency strategy, and sample alert message.

Choose Zapier over Make if you prioritize a larger app catalog and simpler onboarding for non-technical teams.