zapier-israeli-integrations
Zapier Israeli Integrations
Instructions
Step 1: Choose the Right Zap Pattern
Match the Israeli business need to the correct Zap architecture.
| Business Need | Zap Trigger | Action Chain | Israeli Apps |
|---|---|---|---|
| Auto-receipt after payment | Cardcom/Tranzila webhook | Parse payment -> Create Morning doc -> Email customer | Cardcom, Morning |
| Payment reminder (freelancer) | Schedule trigger | Query unpaid invoices -> Filter overdue -> Send Hebrew reminder | Morning, email/SMS provider |
| WhatsApp order confirmation | Payment webhook | Format Hebrew message -> Send approved template | WhatsApp Business or InforUMobile |
Five more patterns (invoice-to-bookkeeping sync, e-commerce orders, expense categorisation, lead capture, multi-gateway consolidation) with full field mappings: references/zap-templates.md.
Single-step vs multi-step. Free gives unlimited Zaps but only two steps (one trigger, one action), 100 tasks/month and 15-minute polling, so it fits "new payment -> log a row" and little else. Almost every automation here needs multi-step, which starts at Professional. Paths (branching) handle the "if the pre-VAT amount is over the Invoice Reform threshold, add an allocation number" shape; keep that threshold in a workflow variable rather than a hardcoded number, so a future change is a one-line edit. Per-plan prices and limits: references/zapier-platform-notes.md.
Use Zapier Copilot to describe what you want in plain English or Hebrew ("when I get a Cardcom payment, create a Morning receipt and email it"). It suggests the structure, finds the apps and maps fields. On every plan, with a daily message limit on Free.