Integration Platforms
Part of Integration platforms and workflow engines
Checking connector limitations before selecting a platform
Check connector operations, fields, licensing, limits and network paths before committing a workflow to a platform.
Before selecting a platform, check a connector against the exact trigger, action, fields and operating conditions your workflow needs. An application’s presence in a connector catalogue is only a starting point. The connector may omit an operation, handle a field differently from the application API, require a particular entitlement or use a network route your environment cannot reach.
List the required operations
Write the workflow as a sequence: source event, any lookup, destination write and the response needed to confirm it. For each step, consult the reference for the specific platform and connector variant you intend to use. Record the operation name and its documented inputs and outputs.
Distinguish triggers from actions; a connector may provide one without the other. Check event wording closely. A record being created, a record being modified and an attachment changing are different requirements.
| Check | Evidence to collect | If it does not meet the requirement |
|---|---|---|
| Trigger | Event covered, filtering, timing and restart behaviour | Find a documented alternative or redesign the intake |
| Action | Exact create, update or lookup operation | Consider another connector route or the application API |
| Fields | Required inputs, returned ID and unsupported structures | Change the mapping only if business meaning remains intact |
| Access | Account permissions, authentication and entitlement | Resolve access or choose another authorised route |
| Capacity | Connector and platform limits for the planned workload | Revise pacing or platform choice using current limits |
| Network | Connection path to the source or destination | Confirm the route with the network owner |
Read the operation’s limitations
Microsoft’s Salesforce connector provides a concrete example. Its reference says the “When a record is modified” trigger does not detect attachment changes on a standard object. It also says its Create record and Update record (V3) actions do not support custom multi-select picklist fields or complex input objects containing nested objects. These are limits of the named Microsoft connector operations, not every route to Salesforce.
Check the connector publisher, known issues, deprecated operations and account-side API access. If a workaround uses a raw HTTP action, assess its authentication, entitlement and maintenance separately.
Check the deployed variant and entitlement
In Azure Logic Apps Standard, built-in and shared managed versions of a connector can expose different operations. Microsoft’s Azure File Storage example has triggers and actions in its built-in form, while its shared managed form has actions only. The forms also use different infrastructure and network paths. Confirm the variant that the workflow will use.
Entitlement is a separate check. Microsoft classifies its Salesforce connector as Premium in Power Automate, while the Power Automate Free licence permits standard connectors only. Other user or flow entitlements may apply. Confirm the licence that will cover the intended flow; the connector’s classification does not state its price or another product’s entitlement.
Capacity also has layers. Power Automate documents platform request limits and says individual connectors have their own limits.
Power Automate counts retries and pagination requests as action runs under its documented request limits. Check the current connector reference and the connected application’s limits against the planned call pattern. A listed limit is not a throughput result for your flow.
Record the decision
For each required step, mark the candidate connector supported, unsupported or unconfirmed, with the exact documentation page and operation. Keep an unconfirmed requirement open until an authorised owner verifies it in the intended environment. Record any fallback route and the maintenance it adds.
Select the platform only when critical operations, access, capacity and network conditions are accounted for.
