Workflow Automation indexes 648 providers at workflow-automation.apievangelist.com — the fourth-largest area on the network, covering the platforms and tooling that move work between systems.
It is one of the strongest-scoring areas we track, and for a structural reason: these companies cannot ship a bad API, because consuming APIs is their product.
The standouts
| Provider | Score | Band | APIs |
|---|---|---|---|
| Appian | 78.0 | Exemplar | 12 |
| Workato | 76.6 | Exemplar | 11 |
| ServiceNow | 76.0 | Exemplar | 63 |
| Microsoft Power Automate | 72.8 | Exemplar | 6 |
| Amazon SWF | 66.6 | Strong | 37 |
| Activepieces | 65.4 | Strong | 9 |
| Robocorp | 61.5 | Strong | 13 |
| Salesforce Automation | 60.9 | Strong | 4 |
| Salesforce Flow | 60.7 | Strong | 5 |
| Tray.io | 58.5 | Developing | 7 |
| Gumloop | 58.4 | Developing | 14 |
| Celigo | 57.9 | Developing | 13 |
Appian tops the area at 78.0 on twelve APIs. Power Automate reaches exemplar on six.
The reciprocity effect
Every company in this list spends its engineering budget integrating other people’s APIs. Workato, Tray.io, Celigo, and Activepieces exist to connect hundreds of SaaS products; their engineers spend their days inside other vendors’ documentation, discovering exactly which omissions cost time.
That experience appears to transfer. A team that has been burned by an undocumented rate limit or an unspecified webhook payload does not ship those omissions in its own API. The area’s scores are, in part, the accumulated result of knowing what bad looks like.
Compare with automotive, profiled today: 42 providers, ceiling 59.4. The gap is not engineering capability. It is proximity to the consumer experience.
Score does not track size
Again the pattern that runs through the whole catalog: Power Automate scores 72.8 on 6 APIs; Amazon SWF scores 66.6 on 37. ServiceNow’s 63 APIs and 76.0 composite show the two can coexist, but breadth is not what produces the score.
The Kin Score measures how completely an API is described. A six-endpoint surface with full specification, named auth, explicit limits, and worked examples beats a thirty-seven-endpoint surface without them.
Where the agents land
Workflow automation is the area most directly reshaped by agents. Gumloop (58.4) and Relay (55.8) are recent entrants building agent-native automation rather than trigger-and-action chains. They sit in the developing band today — young companies with young surfaces — and they are the ones to watch, because an automation platform that agents consume has to be machine-readable in a way a drag-and-drop builder never did.
Takeaway
648 providers, four exemplars at the top, and an area that scores well because its companies consume APIs for a living. If you want to know what good API description looks like, look at the people who integrate everyone else’s for a living.
Browse the area at workflow-automation.apievangelist.com.