Connecting two SaaS tools without writing code is easy. Keeping the connection correct for a year is the hard part.
Integration platforms connect cloud applications with triggers and actions. A form is submitted, so a CRM lead is created and a message posts to Slack. Done well, this removes copy-paste work and keeps everyone looking at the same customer data.
How the platforms work
Trigger-and-action recipes fire on an event: a new row, an updated deal, a scheduled time. Multi-step flows add conditions, filters and branches.
iPaaS tools add what a larger portfolio needs: promoting between environments, proper logging, and access by role.
Deciding what counts as the same record
Agree how records match across systems, whether by email, an external ID or your own key. A stable identity is the thing that keeps duplicates and orphans out.
Transform fields at the boundary. Normalize phone formats, map picklist values, split a full name when the target wants two fields.
- Write down every source and target field mapping
- Choose upsert or create-only on purpose
- Say what happens when a value is empty
- Test the awkward cases: accented names, very long strings, time zones
Assume it will fail sometimes
Rate limits and dropped calls are normal. Retry with a backoff, and tell someone when a record fails repeatedly.
Make each step idempotent. Otherwise a flow that reruns after a partial success bills the customer twice.
Keep a list of what you have built
Keep a catalog: owner, purpose, systems touched, how sensitive the data is. An integration nobody owns is a security problem and an outage waiting to happen.
Check connected app permissions regularly and revoke the OAuth grants nobody uses.
Written by the team at Ambivo, a business platform that keeps CRM, accounting and ERP on one customer record. This article is general guidance on the topic rather than a description of Ambivo features.