Where Salesforce integrations fits on a long engagement.

API limits are the constraint that shapes every Salesforce integration. Daily call allowances are finite and shared across every integration in the org, so a naive implementation making one call per record exhausts the allocation and breaks everything else connected to the platform.

Bulk and composite APIs exist precisely for that, and they are underused. Processing records in batches rather than individually is usually the difference between an integration that fits inside the limits comfortably and one that is permanently near them.

What an assigned team does with Salesforce integrations.

Salesforce orgs accumulate customisation — custom objects, validation rules, triggers, flows — and an integration writing data can trigger automation nobody told the integrator about.

Understanding what fires on write before building is what avoids that, and it is the kind of upfront discovery scoped as part of how the monthly fee is built.

What we use Salesforce integrations for.

  • Bulk operations rather than per-record calls Batched processing that keeps the org comfortably inside its limits.
  • Existing automation accounted for Triggers and flows understood before writing data that fires them.
  • Streaming for near-real-time sync Change events consumed rather than polling on a schedule.

How Salesforce integrations capacity is assigned.

CRM integration is assigned inside development capacity, with API limits and existing org automation established before implementation.

Tell us what your roadmap needs Salesforce integrations for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

Loading the contact form… You can also email hello@azendo.co.

We reply within one working day. No obligation, and no newsletter.