Integrations
System and API Integration
Make the Systems You Already Pay For Talk to Each Other
The same customer detail typed into the CRM, the invoicing system and a spreadsheet is not three records, it is three chances to be wrong. I connect the tools you already run - CRM, invoicing, ERP, WhatsApp, email, Google and Microsoft - so a change in one lands in the others, with retries and alerts for when a service is down.
Key takeaways
- Decide which system owns each field. Two-way sync without an owner produces conflicts nobody can resolve later.
- Every integration fails eventually. Retries, idempotency and an alert are what separate a working one from a silent one.
- Idempotency matters more than it sounds: a webhook delivered twice must not create the invoice twice.
- Zapier or Make is the right answer for simple, low-volume links. Custom wins on complex logic or per-task pricing.
What I build
- CRM to invoicing (Morning / Green Invoice, iCount, Priority, Hashavshevet)
- ERP and accounting integrations, including Priority
- Microsoft 365 and Google Workspace: mail, calendar, files, SharePoint
- Webhook endpoints with signature verification, retries and idempotency
- Scheduled syncs with a reconciliation report so drift is visible
- Monitoring and alerting, so a broken integration surfaces the same day
What it costs
Business automation - one workflow
$300 - $1,800
Days to 1 week
Lead follow-up, invoicing, reminders, reporting
Business automation - multi-step system
$1,800 - $8,000
2 - 5 weeks
Several tools wired together, custom logic, monitoring
Ranges exclude VAT and third-party costs. Every project gets a fixed quote after a scoping call. All pricing · The full guide
Projects I built
BrainStim Centers - Clinic Operations Automation
Three-module automation: PDF questionnaires parser, Rise4→Monday→CharmHealth sync, eClinical reconciler.
Realtor → Google Sheets Daily Extraction + Client Dashboard
Apps Script scraper + branded, password-less client dashboard - one deploy, per-client URL.
ARCS Dental - Inventory & Purchasing System
Tablet counting UI + Flask API + Playwright/Henry Schein cart automation - end-to-end with documented handover.
How it works
A short scoping call
What hurts today, what you already use, and what "done" looks like.
A written fixed-price quote
Scope, price and timeline in writing, approved before any work starts.
Built in stages, on your real data
You see a working first version early, not a demo at the end.
Handover with documentation and monitoring
You own the code and the data, and a support window follows launch.
Working with me from the US or Europe
- Most of my client work is for companies in the US, UK, Germany, the Netherlands and Australia.
- Calls are in English and scheduled in your time zone. My working day covers most of the European one and the US East Coast morning.
- A fixed price in US dollars, agreed in writing before any work starts.
- Pay me directly, or hire me through Upwork if you prefer to work through a platform.
- You own the code and the data, with documentation and a support window after launch.
Guides on this
Practical guides from real client work.
Building a Reliable Data Pipeline (ETL) for Scraped Data
How I build a data pipeline for scraped data: extract, validate, clean, deduplicate, enrich, store. An ETL pipeline that survives dirty, changing data.
System Integration for Small Business: Connecting CRM, ERP and Your Site
How to connect your CRM, ERP, website and apps so the same data stops being typed twice - what goes over an API, what goes over a file, what each option costs, and the order to do it in.
Connecting CRM and ERP to a BI Dashboard: A Practical Guide
Your sales data lives in the CRM and your financial data lives in the ERP, so nobody can answer "which customers are actually profitable?". Here is how to join both into one BI dashboard - the architecture, the real costs, and the mistakes that make these projects fail.
Connecting Your Online Store to an ERP: Shopify and WooCommerce to Priority, SAP B1 and Hashavshevet
Every online order that gets retyped into the ERP is a mistake waiting to happen. Here is how store-to-ERP integration actually works - which direction each piece of data flows, what breaks first, and what it costs to build properly.
Priority ERP API Integration: A Developer's Field Guide
Priority has a genuinely good REST API, and integrations against it still routinely blow their estimates. The reason is never the API - it is that every Priority installation is customised. Here is what to check before you scope, and the patterns that hold up in production.
Israel Invoice (Allocation Numbers): What It Means for Your Systems
An engineering guide to building around Israel's invoice allocation-number requirement: where it sits in your issuance flow, the failure modes it introduces, and how to design so a tax authority outage does not stop you invoicing. Not tax advice - confirm the current rules with your accountant.
Priority ERP Webhooks: Pushing Events Out Instead of Polling
How Priority ERP webhooks actually work - where they are defined, how BPM rules fire them, what headers and JSON body arrive, the 7-day error log, and the retry problem you have to solve yourself.
Priority REST API: The Errors That Waste the Most Time
A troubleshooting reference for the Priority OData REST API - why errors come back as XML from a JSON API, the auto-unique key trap on PATCH, batch limits, authentication combinations that cancel each other out, and how to find real field names.
The monday.com API: What Actually Limits You Is Complexity, Not Calls
A developer's guide to the monday.com GraphQL API - the three required headers, the complexity budget that stops integrations before the daily call limit does, column_values as JSON strings, and how to size a sync that will not die at scale.
Frequently asked questions
Why not just use Zapier or Make?
Often you should, and I will say so. They win on simple connections and speed to first version. Custom wins when the logic has real branching, when the volume makes per-task pricing hurt, when the app you need has no connector, or when a failure has to be retried intelligently rather than emailed to you.
What if one of the systems has no API?
Then the options are a file-based exchange on a schedule, a database-level connection where that is allowed, or browser automation as a last resort. Each has real trade-offs and I will tell you which one you are getting and why, rather than presenting a fragile approach as equivalent.
How do we know it is still working next month?
Because it tells you when it is not. Every integration ships with logging, a retry policy and an alert on repeated failure. The failure mode worth designing against is not an error - it is an integration that quietly stops and is noticed a month later.
Sources
Official documentation you can verify the claims on this page against.
Let us scope your project
Tell me what you need and I will give you an honest scope, price, and timeline.