Systems Integration for Israeli Businesses: What Connects to What

A reference for the software Israeli businesses actually run - Priority, SAP B1, Hashavshevet, Rivhit, Morning, Monday, WhatsApp Business API - what integration each one supports, how hard it is, and which connections are worth building first.

Key takeaways

Integration difficulty in Israel is driven less by the vendor and more by how customised your installation is. A stock Priority is easy; a ten-year-old heavily-extended one is a different project entirely.

Ask three questions before scoping anything: does it have a documented HTTP API, can you get a sandbox, and who inside the vendor can answer a technical question. A "no" on the third one adds weeks.

The highest-ROI first integration for most Israeli SMBs is website or store to invoicing system. It is small, it removes daily manual work, and it proves the pattern before you touch the ERP.

Middleware beats point-to-point past three systems. Five systems wired directly to each other is twenty connections to maintain; five wired to a hub is five.

Most integration advice online assumes an American stack: Salesforce, NetSuite, QuickBooks, HubSpot. Israeli businesses run something different, and the practical questions - can Hashavshevet be automated, does Priority have a real API, how do I get orders into Rivhit - do not have good answers in English or Hebrew.

This is a reference page for what actually connects to what, based on systems I have integrated. It is deliberately opinionated about difficulty, because that is the number that determines your budget.

ERP and Accounting

System	Integration surface	Difficulty	Main gotcha
Priority	REST API, well documented	Moderate	Field and form names are installation-specific
SAP Business One	Service Layer (OData)	Moderate to high	Session handling, strict object model
Hashavshevet	Local API / ODBC / file import, varies by version	Varies wildly	Confirm which surface you have before scoping
Rivhit	HTTP API	Low	Invoicing scope, not full ERP
Morning (Green Invoice)	Modern REST API	Low	Token lifecycle and document-type mapping

The pattern worth noticing: the newer and more cloud-native the system, the cheaper the integration. If you are choosing an invoicing system now and integration matters to you, that should weigh heavily in the decision.

CRM and Operations

Monday.com - excellent GraphQL API, very widely used in Israel, integrates with almost anything. Often the easiest system in the whole stack.
HubSpot and Zoho - mature REST APIs, generous webhooks, standard work.
Salesforce - fully capable, but the effort is in the org's own configuration rather than the API.
Custom or legacy internal systems - typically a database, sometimes an Access file. Integrable, but the honest scoping question is whether to integrate it or replace it.

Storefront and Payments

Shopify and WooCommerce both expose rich APIs and webhooks and are straightforward to connect in either direction. Israeli payment providers vary more: some offer clean APIs and webhooks, others expect a redirect flow with a callback and little else. Verify webhook support before you promise anyone real-time order status.

Messaging

WhatsApp Business API (via Meta's Cloud API) is the one channel that changes how Israeli customers actually reach a business. It is genuinely integrable - template messages, inbound webhooks, media - but it carries its own rules: template approval, a 24-hour service window for free-form replies, and per-conversation pricing. Treat it as a real integration project, not a plugin.

SMS is simpler and still relevant for reminders. Email is trivial to integrate and remains the reliable fallback.

How to Choose What to Build First

Score each candidate connection on three things:

Hours saved per week. Count the actual minutes someone spends copying data, times the frequency. Most people overestimate the glamorous integration and underestimate the boring one.
Error cost. A typo in a marketing list is cheap. A typo in an invoice is not.
Build difficulty. From the table above, plus whether you can get a sandbox.

The winner is almost never the integration people ask for first. It is usually website or store to invoicing - small, daily, and error-prone when manual.

Point-to-Point or Middleware?

With two or three systems, connect them directly. It is less code and less infrastructure.

Past that, the arithmetic turns against you. Connecting five systems directly to each other is up to twenty one-way links, each needing its own error handling and each breaking independently. A hub - n8n, Make, or a small custom service - turns that into five links and gives you one place to see failures. The switch usually pays for itself at the fourth system.

Questions to Ask a Vendor Before You Commit

Is there a documented HTTP API, and can I see the documentation before signing?
Is there a sandbox or test environment, and does it cost extra?
Are there webhooks, or is polling the only option?
What are the rate limits?
Who do I contact with a technical API question, and what is the response time?

The last one matters more than people expect. A capable API with no one to answer questions about it costs more in practice than a mediocre API with a responsive integration contact.

What Integration Costs in Israel

Rough ranges, assuming a freelance senior engineer rather than an agency:

Type	Typical range
One-way, one flow, modern APIs on both sides	Days to 2 weeks
Two-way sync, one legacy system involved	3-6 weeks
Multi-system hub with error handling and monitoring	6-12 weeks

Add ongoing maintenance to every one of these. APIs change, tokens expire, and an unmonitored integration fails silently.

If you want your specific stack mapped and prioritised, book a free call. Deeper reading: the full CRM and ERP integration guide, connecting an online store to an ERP, and joining CRM and ERP into a BI dashboard.

Frequently asked questions

Does Priority have an API I can integrate with?

Yes. Priority exposes a documented REST API covering orders, customers, items, stock and most standard documents, and it is the smoothest of the Israeli ERPs to integrate against. The practical difficulty is not the API itself but your specific installation: Priority deployments are heavily customised, so the field you need is often a customer-specific extension rather than a standard one. Get a sandbox and a field list from your Priority partner before scoping any project.

Can Hashavshevet be automated?

Usually yes, but the method depends entirely on your version and installation. Depending on what you have, the integration surface may be a local API, an ODBC connection to the underlying database, or a file-based import routine. These are very different projects with very different costs. Establishing which one applies to you is the first step of any scoping conversation - this single fact can double or halve the estimate.

When should I use n8n or Make instead of writing custom code?

Use a platform when the flows are mostly standard, the data volume is modest, and you want visibility and quick changes without a developer for every tweak. Write custom code when you need complex transformation logic, high volume, tight control over retries and idempotency, or when you are integrating a system with no ready connector. A very common and sensible answer is both - a platform for the simple flows and a small custom service for the one hard integration.

How do I know if an integration is worth building?

Measure the manual work honestly before estimating the build. Count the minutes per occurrence and the occurrences per week, then multiply by a realistic hourly cost. Add the cost of the errors the manual process produces - a wrong invoice, a lost order, a customer told the wrong stock level. If that annual number is a meaningful multiple of the build cost, it is worth building. If it is close, it is usually not, because you also inherit ongoing maintenance.

What breaks integrations most often?

In order: expired or rotated credentials, a vendor changing a field or endpoint without notice, rate limits hit during an unusual traffic spike, and unhandled edge cases in the data such as a missing tax ID or a product that exists in one system but not the other. All four are survivable if the integration has retries, a visible error queue and alerting. Without those, the same four causes produce silent data loss instead.