Work Area
API Integrations
We connect your tools so they share information directly and nobody types it twice. Your website, customer records, payments, and accounts stay in step, and every connection we build is monitored, so a failure is noticed and fixed instead of discovered weeks later.
- 1,200+ clients helped
- Building since 2010
- 15 services, one team
- 50+ technologies
At a glance
What we build
We build integrations that let two programs exchange information directly, through an API (a set of agreed requests one program can make of another).
Problems we solve
Information is typed into one tool, then again into another, and the copies drift apart.
Who we serve
Teams that use several tools for one process, and technical leads who need those tools to share data reliably.
How to choose
Connect tools when the same data lives in two places. Build a shared record when many tools need to agree.
In practice
Programs that talk to each other
We connect two programs so one can send or request information from the other automatically. The API is the agreed set of requests the programs use, a bit like the menu a kitchen accepts orders from.
Most business tools offer an API. An integration uses it so that a sale in your store creates an invoice in your accounts, or a new customer in your records appears in your email tool.
The skill is not only making the connection. It is deciding which tool is the source of truth for each fact, and handling the cases where something fails.
Tools connected into one flow of information
Your connected tools connected to: Customer records: Who your customers are.; Accounting: Invoices and payments.; Online store: Orders and stock.; Email and messages: Notices and replies.; Payments: Taking and recording money.; Your own systems: Anything built for you..
- Customer recordsWho your customers are.
- AccountingInvoices and payments.
- Online storeOrders and stock.
- Email and messagesNotices and replies.
- PaymentsTaking and recording money.
- Your own systemsAnything built for you.
How it works
What happens when one tool tells another
Every integration follows a similar short path, with checks along the way.
What happens when one tool tells another
A sequence of 5 steps. Something changes: A sale is made or a record is edited.; A message is sent: The first tool tells the second what happened.; The message is checked: Is it valid, complete, and from a trusted sender?; The second tool updates: It records the change.; Success or failure is logged: Failures are retried or reported to a person..
- Something changesA sale is made or a record is edited.
- A message is sentThe first tool tells the second what happened.
- The message is checkedIs it valid, complete, and from a trusted sender?
- The second tool updatesIt records the change.
- Success or failure is loggedFailures are retried or reported to a person.
What it looks like
A shared record kept in step by integration
An integration is best judged by what it leaves behind: one record that agrees across tools.
What goes wrong
Four problems we design against
Duplicates
- The same sale recorded twice.
- We make each message safe to receive again.
Missed messages
- The other tool is down for an hour.
- We retry, and alert if it keeps failing.
Changing rules
- Tools change how their API works.
- We watch for updates and test connections regularly.
Disagreeing records
- Two tools hold different versions of a fact.
- We decide the source of truth for each field.
Choosing
Ready-made connector or custom integration?
Many tools can be connected without writing code. Others need custom work.
What do your tools offer?
Choose this when
Both tools are popular, and the connection you need is common.
- What you get
- A connection set up in an automation platform, fast and inexpensive.
- Keep in mind
- You depend on the connector's limits and pricing.
Choose this when
A tool lacks a connector, or has special needs.
- What you get
- A small custom integration, built and monitored by us.
- Keep in mind
- It needs maintenance when either tool changes.
Choose this when
Five or more tools share the same customers or orders.
- What you get
- A shared data layer, so each tool connects once instead of to every other.
- Keep in mind
- It is a larger project, so plan it with care.
A typical example
Three customer lists kept in step
A typical case is a business whose online store, accounting software, and email tool each hold a list of customers. Staff update all three by hand, and the lists no longer match.
An integration could make the store the source for new customers, pass each sale to accounting, and add the customer to the email tool if they agree. The three lists would stay in step.
Technology
Under the hood
For your developers and IT lead: our choices on styles of connection, reliability, and security, and the reasoning behind each.
We work with REST and GraphQL interfaces, and with webhooks, which let one tool notify another the moment something changes.
- Retries with limits, and a queue for messages that cannot yet be delivered.
- Each message carries an identifier, so repeats are ignored.
- Logs and alerts that show what was sent and what failed.
- Keys are held in a secrets store and rotated.
- Each connection has the minimum permissions it needs.
Tell us which tools should talk to each other
List the two or three tools your team switches between most. We will say what can be connected and what it would take.