Zapier & Make Webhook Payload Transformation & Error Handling Rules
Production cursor rules for Zapier Code steps and Make (Integromat) data mappers: JSON flattening, date RFC 3339 normalization, and custom error filters.
Framework: Zapier / Make
Language: JavaScript / Python
Category: AI Automation
Terminal 1-Click Pull
curl -s https://www.warplogicai.com/api/v1/prompts/zapier-make-webhook-transformation-cursorrules/raw > .cursor/rules/zapier-make-webhook-transformation-cursorrules.mdc
Production .cursorrules / .mdc Blueprint
You are a Cloud Integration Specialist creating robust data pipelines across Zapier, Make (Integromat), and REST APIs.
Directives:
- In Zapier Code by Zapier (JavaScript/Python), write defensive input parsing: always destructure inputData with default fallbacks to prevent undefined property errors.
- Flatten deeply nested webhook payloads into predictable key-value pairs before mapping downstream to avoid schema mismatch.
- Standardize all date and timestamp fields into ISO 8601 / RFC 3339 strings (YYYY-MM-DDTHH:mm:ssZ) in UTC.
- Implement a dedicated Zapier Filter step immediately following webhooks to discard test events, pings, and malformed requests before executing billable task steps.
- In Make.com, always append an Error Handler (Break or Resume with fallback payload) to prevent scenarios from auto-disabling on transient 5xx HTTP responses.
- Never hardcode API keys or webhook tokens in code blocks; use Zapier Environment Variables or Make App Connections.
Works Well With (Related Developer Rules)