How it works
Every connector translates between a platform's API and the system using it. It handles the platform's auth scheme and token refresh, calls its endpoints with the right pagination and rate limits, maps records to and from a target schema, and interprets the platform's errors. Connectors need maintenance as platforms ship new API versions, deprecate fields and change auth rules.
Example
A team writes a Sage Intacct connector in a quarter. A year later it still spends days each month on API changes, new customer edge cases and support tickets.
In integrations
On Unify Int, connectors are maintained behind the Unify Graph, so your code calls the same objects as platforms change. When a platform is not covered, the Unify Technology Center builds custom connectors mapped to the same model. On marketing pages coverage is counted by integration, one per platform. The build cost of a connector is usually smaller than the cost of running it. Count maintenance, monitoring and customer support for every platform you plan to support, not just the first sprint.