Every form that writes to Salesforce spends API calls, and those calls draw from an allowance that the whole org shares. The Salesforce limits reference describes two kinds of limits: concurrent limits on long-running requests and total allocations over a rolling 24-hour period. Form teams that understand both can size an integration before volume grows, and they can spot the cause when Salesforce returns a request limit error.
The Two Limits
The first limit caps concurrent requests that run for 20 seconds or longer. Production orgs allow 25 such requests at once, and developer and trial orgs allow five. Salesforce does not limit concurrent requests shorter than 20 seconds. When long-running requests exceed the cap, the API returns a REQUEST_LIMIT_EXCEEDED code until the count falls.
The second limit caps total requests in a rolling 24-hour period, and the cap depends on the edition and the number of licenses. Salesforce gives one example: an Enterprise Edition org with 15 licenses has a limit of 115,000 requests, which is 100,000 plus 1,000 for each license. The count covers every integration that calls the org, so a form platform shares the allowance with reporting tools, data syncs, and every other connected app.
What a Form Submission Costs
Each submission spends several calls. FormAssembly documents the pattern in its guide to API calls for the Salesforce Connector: one call to authenticate, one call for each lookup or create on an object, and two calls for each update on an object. The guide gives an example in which a connector that updates a contact and creates an attachment record makes four calls.
A simple illustration shows the scale. A form that makes four calls and receives 1,000 submissions in a day uses 4,000 calls, which is about 3.5 percent of the 115,000-call example above. A campaign that sends 20,000 submissions in a day with the same design uses 80,000 calls and leaves little room for anything else in the org.
How to Stay Inside the Limits
Teams control usage in four ways. They remove lookups that the form does not need. They skip connector steps when a condition makes them pointless, which FormAssembly supports with a skip-if formula. They use a dedicated integration user, so usage is easy to trace. And they watch the numbers: Salesforce shows the API requests from the last 24 hours in Setup, and the REST API exposes a limits resource that returns the same information to a monitoring script.
Where FormAssembly Fits
FormAssembly connects directly to Salesforce, so its call counts follow the documented pattern and teams can plan from it. The connector supports skip-if formulas, a secure API user, and API version control, and the audit trail records each submission and connector result.
For Salesforce admins who share one org across many integrations, that transparency makes capacity planning a calculation instead of a guess. Admins who expect a spike, such as a registration deadline, should multiply expected submissions by the calls each form makes and compare the result with the daily allowance before launch.
Explore FormAssembly’s capabilities for yourself
Book a personalized demo or request a free trial today.
