👤 For teams creating and maintaining integration connections
🔐 Service Account management requires Super Admin; integration access depends on account permissions
🎯 Plan execution capacity, authentication, and connection maintenance
A purchasing integration may need to keep running after its original owner changes teams. At the same time, an initial data load can generate far more work than the daily operation. Planning authentication and execution capacity helps the team handle both situations.
By the end of this article, you will know how to consider execution limits, separate integration credentials from personal accounts, and organize access and maintenance for your flows in Pipefy Integrations.
📖 What you will understand here:
How Pipefy Integrations processes executions (and the limits that shape your flow design)
Understanding how the platform executes a flow, and within which envelope of time, memory, and concurrency it operates, is what separates an integration that scales from one that breaks in production.
How the platform processes executions
Distinguish receiving an event from completing the work it starts. An acknowledgment tells the originating system that the request was received; it does not, by itself, confirm that every subsequent action has finished.
Define whether the originating system can continue after acknowledgment or needs a business result before proceeding. This choice determines what must be included in the response path and what can be processed afterwards.
The official limits table gives a flow 30 seconds to acknowledge an incoming webhook trigger. Treat acknowledgment separately from the completion time of the flow. Plan slow external calls and heavier processing around the response contract required by the originating system.
The limit of 50 simultaneous executions
The official limit is 50 concurrent executions per company in shared environments, identified as Multi Tenant or MT. The documentation explicitly excludes dedicated Single Tenant or ST configurations from this concurrency control. Confirm which environment applies before using that number to plan a load.
For bulk operations, consider how many executions can overlap and how long each one stays active. A batch size alone cannot establish the expected waiting time or guarantee that a queue will not form.
Start with a small representative batch, observe execution duration and waiting time, and adjust volume and intervals. Account for other active flows using the same capacity. Choose batch sizes from those observations rather than a fixed number for every process.
Governance limits that affect flow design
Beyond the concurrency limit, certain technical parameters define the operating envelope for each individual execution.
5 minute timeout per execution
The Integrations Limits table lists a maximum of 5 minutes for a flow execution. Use that documented reference when assessing whether the work needs to be divided. Check the current table for the environment used before changing a production integration.
Split long work into smaller units and assess subflows for independent responsibilities. Smaller batches and a defined recovery path make maintenance easier. A loop inside one execution does not automatically give each iteration a new execution limit.
512 MB of RAM per execution
The documented memory limit is 512 MB per execution. When handling large JSON payloads or files, consider the memory used by transformations as well as the input size. Load only the information required for the next action.
The 10 MB file limit is scoped to the Files Utility. It is not a guarantee that larger files can be processed through any other path: memory and the capabilities of each connector still matter. Where supported, use signed URLs and streaming to avoid keeping an entire file in memory.
Plan initial loads separately from daily traffic. Monitor responses from connected APIs, apply their rate limits, and define how to retry or investigate rejected requests. Keep the execution record so the team can identify what completed and what still needs attention.
Use the official limits table together with the flow performance recommendations when planning volume, memory, and work division.
Service Account: authentication without personal credentials
A Service Account is a service account created specifically to authenticate integrations. It does not represent a human user. It has its own email address, a Client ID, and a Client Secret, and it is this combination that Pipefy Integrations uses to authenticate and operate within the pipes it needs to interact with.
Using a Service Account separates integration authentication from an employee's access. This reduces dependency on a particular person, but the account still needs an owner for maintenance. Disabling it or changing its access can interrupt every connection that uses it; identify those dependencies before making changes.
Naming and permissions: decisions that matter before you create
Two points deserve attention before creating the first Service Account, because they are difficult to correct after integrations are already in use.
Use a descriptive account name and record its purpose, connected systems, and technical owner in the description. The description is optional in the product; filling it is a governance recommendation. Name integration connections with the standard prefix, for example [Service account] Purchasing ERP.
Creating and managing Service Accounts requires a Super Admin. The account itself has a role and must have access compatible with the resources and actions used by the integration. Review these permissions for the actual connection rather than treating Pipe Administrator as a universal requirement for every API operation. See the Service Accounts guide.
Organize credentials and connection maintenance
Client ID identifies the account, Client Secret is a sensitive credential, and the token authorizes authenticated requests during its validity period. With Client Credentials, the integration obtains a token from the token endpoint. Plan expiration checks and token renewal; possessing the account credentials does not make a token permanent. The Developers guide explains this lifecycle.
As a modeling recommendation, organize accounts by department and distinguish internal use from external connections where their responsibilities and access differ. For example, separate an internal purchasing integration from a supplier connection. Keep secrets in the approved connection or credential management mechanism, with controlled access.
Maintain an inventory linking each account to its connections, pipes, flows, technical owner, and renewal process. Review legacy connections proactively. Before replacing or disabling credentials, test the new connection with the required actions and plan the transition. This keeps account maintenance separate from replacing a human approver.
Before moving on, confirm that you understand
☐ The scope of the concurrency limit and how execution duration affects load planning.
☐ Why the 5 minute timeout affects the design of flows with high data volume
☐ The difference between a Service Account and a Pipefy user's credentials
☐ Who manages the Service Account, what access the integration needs, and how tokens and dependencies are maintained.
Ready to connect the information used by each step? Data Mapping


