Make

Role: You are an automation engineer building a Make scenario to route incoming lead webhooks into a CRM. Constraints: use a Webhook trigger, at most 4 modules, no iterators/aggregators, preserve original payload as metadata. Output format: provide a numbered list of modules (module name, exact settings, field mappings) and a single example mapping block. Example mapping: {"email": "Contact Email", "first_name": "First Name", "lead_source": "Lifecycle Source"}. Also include one conditional filter example for facebook vs. organic leads and the exact filter expression to use in Make.

Role: You are a Make scenario designer creating a scheduled daily export of new ecommerce orders to an SFTP server. Constraints: run once daily, include only orders created in the last 24 hours, output must be a UTF-8 CSV with headers, use at most 5 modules. Output format: produce a step-by-step module sequence (trigger schedule, query module or HTTP, CSV builder settings, SFTP upload settings) and include the exact CSV header row and an example CSV line. Example header: order_id,created_at,customer_email,total,currency. Provide the date filter expression to select last-24-hour orders.

Role: You are an integration specialist building a Make scenario that enriches incoming leads via the Clearbit Enrichment HTTP API, then deduplicates and upserts into CRM. Constraints: respect Clearbit rate limit (max_concurrent_requests = 5), include exponential backoff retries (3 attempts), and ensure a single dedupe key (email). Output format: return a JSON array of modules with fields: {"module":"name","config":{...}}, include HTTP module settings (endpoint, headers, query), backoff policy, and a sample HTTP request/response pair. Also include the dedupe logic pseudocode (input array → unique by email → upsert mapping).

Role: You are a product operations lead designing a Make scenario to sync ecommerce orders to an ERP in 100-order batches. Constraints: batch size = 100, implement idempotency via order_id hash, include per-batch retry policy (5 retries, linear 30s interval), and mark failed batches in a Google Sheet. Output format: provide an ordered list of modules with aggregator settings (size=100), idempotency key formula, HTTP/ERP payload template, and exact Make expressions for retry and failure logging. Include a one-line example of the ERP batch JSON payload for two orders.

Role: You are a Senior Integration Architect building a Make scenario that aggregates high-frequency webhook events into periodic analytics payloads. Requirements and constraints: accept webhooks continuously, buffer and aggregate by event_type over a 5-minute sliding window, produce a compressed JSON summary (counts, uniques by user_id), retry failed analytics HTTP calls with exponential backoff up to 6 attempts, and include monitoring alerts on >10% dropoff. Output format: deliver a scenario blueprint listing modules, aggregator configuration (window type=sliding, length=5m), iterator usage, HTTP module body template, pseudocode for aggregation, and two small examples: raw webhook events (3 items) and resulting aggregated JSON. Also include the exact Make expressions for windowing and timestamp alignment.

Role: You are an integration architect creating a Make workflow to sync inventory updates from webhooks into an external database/API with transactional upsert semantics. Constraints: ensure idempotency, support conflict resolution (last-write-wins or delta merge), include conditional branching for negative stock/errors, and provide SQL-like upsert logic. Output format: give a full module sequence, conditional flow logic, example SQL upsert statement or HTTP PATCH body, error handling and rollback approach, plus a few-shot example: (1) webhook event, (2) current DB row, (3) resulting upserted row. Also include the idempotency key formula and how to store it.

Compare Make with Zapier, n8n, Pipedream, Workato, Power Automate. Choose based on workflow fit, pricing limits, integrations, governance needs and whether the output must be production-ready or only assistive.