HubSpot, Pipedrive, Salesforce
Contacts, deals and activities to and from your other systems.
CRM
Dev & appsAPI integration development that keeps running.
Your online store, CRM, accounting and planning exchanging data on their own. With error handling, logging and an alert when something goes wrong, so nobody retypes anything and nothing gets stuck unnoticed.
Integrations with error handling and monitoring. From €2,500 excl. VAT.
Custom integration from €2,500 excl. VAT · with monitoring
- Based in Julianadorp, NL · Chamber of Commerce 54099897 · you talk to the people who build it
In short
What is an API integration?
An API integration lets two systems exchange data automatically, for example an order from your online store that arrives as an invoice in your accounting. Sharp Creations builds custom integrations from €2,500 excl. VAT, with error handling, logging and monitoring. If a standard connector or a tool like Zapier or Make is enough, we will advise that. We are based in Julianadorp (the Netherlands) and work for businesses across the country.
Mainly want to link two apps quickly? See connecting apps.
Choosing
Standard connector, Zapier or custom?
| Standard connector | Zapier or Make | Custom | |
|---|---|---|---|
| What it is | A built-in link between two packages | Flows you click together yourself | Your own code calling both systems’ APIs |
| Quick to go live | Yes | Yes | Longer |
| Costs | Often in your subscription | Usage-based subscription | Build up front, then hosting and maintenance |
| Volume and logic | Whatever the maker designed | Low volumes, simple rules | High volumes, complex rules |
| When it fails | Little insight | An error per flow | Logging, retries and alerts to suit |
| Choose when | It does what you need | It is small and not business-critical | Invoices, stock or customer data must be right |
More on the trade-off: Zapier, Make or custom.
Technology
How we build integrations that keep working.
APIs and webhooks
An API is a system’s official entrance: you request data or send it. With a webhook a system reports by itself that something happened, such as a paid order, so the integration reacts straight away instead of checking every few minutes. We use REST or GraphQL, depending on what the system offers, and authenticate with OAuth or API keys that we store securely.
Error handling
Systems sometimes go down briefly or report too many requests. A good integration retries later, with gradually longer pauses, and prevents an order arriving twice if a message is sent twice. If it still fails after a few attempts, the message goes into a queue for a person.
Monitoring
Every sync is logged. If something goes wrong, you or we get an alert, before a customer notices.
Data mapping
A customer in your online store is not the same as a contact in your accounting. We record which field goes where, which system is the source of truth and what happens when data conflicts.
Maintenance
APIs change: new versions arrive and old ones disappear. With a maintenance agreement we keep your integrations up to date; the amount is in the quote up front.
Systems
Systems you can connect.
Shopify, WooCommerce
Orders, customers and stock to accounting, ERP or CRM.
ONLINE STORE
Exact Online, Moneybird, e-Boekhouden
Invoices and payments automatically in the right place.
ACCOUNTING
AFAS, Exact, Microsoft Dynamics
Products, prices and stock as the source for your store or portal.
ERP
Mollie, Stripe
Payment statuses that update your orders and CRM straight away.
PAYMENTS
Mail, sheets and planning
Mailchimp, Klaviyo, Google Sheets or your planning tool. If a system has an API, we can usually work with it.
OTHER
What you get
What you get.
01
An integration plan
Which data, in which direction, and which system is the source of truth.
02
The integration, tested
Tested with test data, including the edge cases.
03
Error handling
Retries, no duplicate records and a queue for what a person needs to see.
04
Logging and alerts
You see what was synced, and get notified if something goes wrong.
05
Documentation
How the integration works, so another developer can maintain it too.
06
Your code
Once paid, in a Git repository.
How we work
How we build your integration.
- 01
Mapping
Which systems, which data and what happens by hand today.
- 02
Fixed price
The integration plan with a fixed price and planning.
- 03
Build and test
In test environments where possible, edge cases included.
- 04
Launch and monitor
Launch with logging and alerts, and adjustments in the first weeks.
Examples
Examples of integrations.
- A paid order in your online store automatically becomes an invoice in your accounting.
- A won deal in your CRM creates a project in your planning tool.
- Stock from your ERP updates your online store automatically.
- An enquiry through your website arrives as a contact in your CRM, with its source.
These are general examples. In our cases you can see forms that land straight in HubSpot, such as the registrations at Experience Zorg and the booking and membership requests at ARENI Winestorage. Need data moved once into a new system? We do that too: contacts, deals and history, deduplicated and cleaned.
From our work
Integrations in our work.
CARE · NORTH HOLLAND
Experience Zorg
Registration forms that land straight in HubSpot.
SCANDINAVIA
ARENI Winestorage
Booking and membership requests linked to the HubSpot CRM.
ONLINE STORE · TEXEL
Hondenvoeding Texel
A custom online store with stock, delivery and shipping.
These are the integrations inside these projects; a public case of a standalone API integration is not on the site yet.
All casesPrice
What drives the price.
A custom integration starts at €2,500 excl. VAT. What determines the price:
- the number of systems, and whether data flows one way or both ways;
- the volume of data and how often it must sync;
- how good the systems’ APIs are;
- historical data that needs a one-off migration;
- requirements for monitoring and alerts.
If a simple flow in Zapier or Make is enough, it costs less; see connecting apps.
Who you talk to
You talk to the developers.
No account manager in between. Call, message or email; you usually get an answer within one working day.
One number for the four of us. We reply within one business day. Based in Julianadorp; online, or we come to you.
Frequently asked questions
Good to know.
Question not listed? Just ask, one of the four of us will answer.
Ask your questionWhat does an API integration cost?
A custom integration costs from €2,500 excl. VAT, with a fixed price up front. The price depends on the number of systems, the direction of the data and how good the APIs are.
What is the difference between an API and a webhook?
Through an API you request data from or send data to a system. A webhook works the other way: the system reports by itself that something happened, so your integration can react straight away. Good integrations often use both.
When is Zapier no longer enough?
When a lot of data flows through, when the logic gets complicated, or when an error costs money or customers, as with invoices or stock. Then you want your own error handling and monitoring.
What happens if one of the systems is briefly down?
The integration retries later. If it still fails after a few attempts, the message goes into a queue and someone gets an alert. That way no message gets lost and we prevent duplicates.
Can you also migrate data once?
Yes. We migrate contacts, deals and history to a new system, deduplicate where needed and make sure you start with clean data.
Do you need access to my systems?
Yes, with as few permissions as needed: an API key or an OAuth connection you can revoke yourself. A data processing agreement is available on request.
Who maintains the integration when an API changes?
With a maintenance agreement we do; the amount is in the quote up front. Without one, your own developer can take over, as the code and documentation are yours.
Which systems do you want to connect?
Name the systems and what happens by hand today. You usually hear back within one working day, with a fixed price or a few focused questions.