API integration: connector, automation or custom build?
Check for a connector first. If one does the job, we'll tell you.
Most popular tools have a plugin, an app or a Zapier step that moves the basics. If that covers what you need, use it. It's cheaper and the vendor maintains it. Our integrations hub explains the five ways we connect systems and the trade-offs of each.
A custom integration is worth building when:
there's no connector, or the one that exists moves half the fields you need;
the data needs rules on the way through: matching duplicates, mapping one system's categories to another's, deciding which system wins when both change;
the volume makes per-task automation pricing expensive;
the data has to stay in Canada, or pass through as few third parties as possible;
the integration is part of what you sell.
Custom API development is the other half of the job. Sometimes the system you need to connect has no API at all, only a database or a nightly export. We build a small, documented API in front of it so your other tools can read from it safely. Both start with integration consulting: we map what should move where.
CRM integration
Most CRM integration requests start with a website form and end with a sync.
The simplest version is one-way: a form or booking on your site creates a contact in the CRM, with the page it came from, the campaign that brought the visitor and the consent they gave. Our own site sends every booking and contact form to our CRM this way, with a Slack alert if a send fails.
The deeper version is two-way. A member's status, a donation or an event registration changes in the CRM, and the website shows it. Most of the work is deciding which system owns each field, what happens when a record is edited in both places, and how to catch a change a webhook missed. CHF BC's Co-op Explorer reads co-op records from Salesforce every day, so staff update a listing in one place.
Salesforce, HubSpot, Pipedrive, Microsoft Dynamics 365 and donor CRMs like Raiser's Edge NXT each have their own page under integrations, covering what the API can and can't do. This page is about the build.
ERP and accounting integration
For most of our clients, ERP integration means the accounting system.
The usual job covers invoices raised in a CRM or a custom app, payments taken through Stripe, and GST or HST that has to land in the right account. We've built Xero integrations for MODERNSPEAK, Zephy and our own business; QuickBooks Online and Sage have APIs that work the same way. We agree the tax and account mapping with your bookkeeper before we build.
MODERNSPEAK's operating system raises invoices in batches and syncs both ways with Xero, so commissions and tax stay in step with the books. For larger ERPs, we usually work alongside the team that runs the ERP: they expose the data, and we build the website or portal side.
A single integration usually takes a few weeks. One that's part of a website or software build ships with that project.
01
Map the data (week 1)
We list every system, record and field involved, and who edits what where. You give us admin or sandbox access to each system and the spreadsheets people use now.
You keep: a field map and a written list of which system owns each field.
02
Test against sandboxes
We move real sample records through test accounts and show you the awkward cases: duplicates, missing fields, records edited in both places. You decide how each one is handled.
You keep: the test results and the rules you chose.
03
Build
The integration runs on a server, with keys kept out of the browser, retries for failed calls, a log of every run and an alert when something fails. You review it on staging.
You keep: the code in a repository you own and the credentials in your accounts.
04
Backfill and switch on
We bring existing records across, compare counts between the systems with your team, and switch the live sync on.
You keep: a reconciliation report showing what moved.
05
Watch and hand over
We watch the first two weeks of live runs and fix what turns up. Then you get the docs, and we stay on for changes if you want us.
You keep: a runbook covering what each job does, where alerts go and what to do when a vendor changes its API.
Results from integrations we've built
These numbers come from the published case studies of projects we built.
Daily
Salesforce sync behind CHF BC's map of 287 co-ops
30 min
Between intranet news syncs to De Havilland Canada's staff page
~20 hrs
Manual work saved a month at Hopewell Residential, across brochures and ad feeds
2-way
Xero sync keeping MODERNSPEAK's books, tax and commission in step
What we check before switching it on
Most integrations that fail stop without telling anyone. These checks catch that.
Keys stay on the server
API keys and tokens live in server settings in your accounts, never in the browser or the page source.
One owner per field
Each field has one system that wins. Without that rule, two-way syncs overwrite good data with old data.
Failures get noticed
Failed calls retry, every run is logged, and a person gets an alert.
Limits and volume
We check each API's rate limits and pricing tier against your real volume, including the backfill and your busiest day.
Personal data
Only the fields that are needed move, through as few services as possible, with Canadian hosting when privacy law, a funder or your board requires it.
Consent travels with the record
Email consent from a form reaches the CRM with its date and wording, so your list stays CASL-compliant.
Vendor changes
We pin API versions, watch vendor changelogs and note in the runbook which calls depend on what.
What an integration costs
We price an integration after mapping the data, because the cost depends less on which tools are involved than on the rules between them. You get a fixed price before we build. An integration inside a website or software project is priced as part of that project. Registered charities and nonprofits get 10% off.
Direction
One-way pushes are quicker than two-way syncs that need conflict rules.
Rules and cleanup
Duplicate matching, field mapping and data that needs fixing on the way through.
Volume and freshness
Real-time webhooks or a nightly batch, and how many records move each day.
Backfill
How many existing records come across, and how clean they are.
Running costs are separate: API plans, automation tools and hosting. We list them before you sign.
Rob & the rest of the Paper Crane team have been invaluable to our success! They've helped us build our vision from the ground up, and walked us through it every step of the way. They built a sophisticated backend system that orchestrates multiple complex data sources while optimizing it for easy use on the front-end.
Between all the complex features they've built and the seamless Ui/Functionality they've been nothing short of excellent. For anyone needing a development partner who can build complex, multi-source data platforms with user-friendly management interfaces, Paper Crane is the best choice out there!
Jake Austin · Google ·
5 out of 5 stars.
I've worked in the agency space for a long time, and with partners of all shapes and sizes.
Rob, Tara and the rest of the team are top-notch. They have a LOT of technical acumen, have watertight ops, and are all-round good humans. They punch above their weight in terms of development, automation, AI deployment and strategy.
If you're considering hiring them, my advice would be you should.
Jake Surrey · Google ·
5 out of 5 stars.
Rob and the team at Paper Crane Media have been fantastic to work with as they handled the redesign of our website. They also provided a wealth of knowledge and expertise on integrations that have streamlined our work flow. I highly recommend Paper Crane, and I can't thank them enough.
Cass Smith · Google ·
5 out of 5 stars.
I worked with Robert and the rest of the Paper Crane team on website, marketing automation and CRM projects and they have been great to work with. They always respond promptly and execute projects in a timely manner. They are very knowledgeable and provide detailed explanations of the steps they are taking. 10/10, highly recommend!
It's connecting two pieces of software through their APIs, the interfaces each one publishes for other programs to use, so data moves between them automatically. A form on your website creating a CRM contact is a simple API integration. A two-way sync between your CRM and your accounting is a bigger one.
What is CRM integration?
Connecting your CRM to the other places customer data starts or ends up: your website forms, booking tools, payment processor, email platform and accounting. The aim is one record per person, kept current without anyone retyping it.
Do we need custom work, or will Zapier do?
Often Zapier, Make or the vendor's own plugin is enough, and we'll say so. Custom work pays off when no connector moves the fields you need, when the data needs rules on the way through, when per-task pricing gets expensive at your volume, or when the data has to stay in Canada.
Is ETL the same as API integration?
Not quite. ETL (extract, transform, load) copies data in batches, usually into a database or reporting tool. API integration usually moves records as they change. Many of our integrations do both: webhooks for live changes and a scheduled check that catches anything missed.
How much do API integration services cost?
We give you a fixed price after mapping the data, because the rules between systems drive the cost more than the tools do. An integration that's part of a website or software build is priced inside that project.
How long does an integration take?
A single integration usually takes a few weeks from data mapping to switch-on, with two weeks of watching live runs after that. Integrations inside a larger build ship with the build.
Who owns the integration, and what happens when an API changes?
You do. The code is in a repository in your name, and the keys are in your accounts. The runbook lists which vendor APIs it depends on. When a vendor changes something, we or any developer you choose can update it.
Can you build an API for our own system?
Yes. If a system only has a database or an export, we can build a small, documented API in front of it so other tools can read it safely. That's custom API development, and it's often the first step of a bigger integration.
Where does our data go?
Only to the systems in the integration and the server that runs it. We move only the fields that are needed and choose Canadian hosting when your privacy rules, a funder or your board require it.
Can you work with our CRM admin or Salesforce partner?
Yes. Often the CRM is configured by an admin or partner, and we build the website, portal or middle layer that talks to it. We agree the field map with them before we build.
Have two systems that should be talking to each other?
Book a 30-minute call with our Calgary team. Tell us which tools you run and what your team retypes between them, and we'll tell you whether a connector will do or it needs a build.
We use cookies to see how the site is used and to measure our ads. Accept, or decline and we'll keep to the cookies the site needs to work. Privacy policy