Workflow Automation
Providers using this tag (215)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 15 Complete, well-documented, and agent-ready
Strong 21 Solid coverage with minor gaps
Developing 52 Usable, with meaningful gaps to close
Thin 35 Limited public surface area
Emerging 56 Early or largely undocumented
Minimal 35 Almost no public developer surface
Unrated 1 Not yet scored
APIs with this tag (28)
Ranked by the provider's API Evangelist rating — the Kin Score is scored per provider, not per API, so every API of a provider shares its band. How the rating works →
Strong 4 Solid coverage with minor gaps
Developing 9 Usable, with meaningful gaps to close
Thin 5 Limited public surface area
Emerging 8 Early or largely undocumented
Minimal 2 Almost no public developer surface
Companies reaching this through an API (7)
These companies publish an API, specification or operation carrying “Workflow Automation” but do not classify their business under it. Listed unranked and kept out of the count above, because one tagged operation is not a statement about what a company does.
Score breakdown
Where this tag sits
215 providers carry this tag directly, and 255 counting the 5 narrower tags below — 40 more to reach.
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 212 providers in the APIs.io catalog tagged Workflow Automation, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Access Clarity | 39.2 | 26.5 | +12.7 | 212 |
| Developer Ergonomics | 34.7 | 23.2 | +11.5 | 212 |
| Operational Transparency | 23.9 | 13.7 | +10.2 | 212 |
| Contract Quality | 27.5 | 17.6 | +9.9 | 212 |
| Discoverability | 62.2 | 58.1 | +4.1 | 212 |
| Contract Governance | 9.7 | 6.3 | +3.4 | 212 |
A facet is averaged over the members that carry it, not over the whole cohort — the “Scored” column is that count. Averaging an absent facet as zero would score our own coverage gaps as the providers’ posture.
| Artifact | This cohort | Catalog | Difference |
|---|---|---|---|
| MCP server (any) | 26% | 14% | +12 |
| MCP server (first-party) | 23% | 12% | +11 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 18% | 11% | +7 |
| Security | 99% | 98% | +1 |
| Arazzo workflows | 5% | 2% | +3 |
| Governance rules | 18% | 14% | +4 |
mcp_pct counts any mcp/ artifact including ones API Evangelist derived from the provider OpenAPI; mcp_first_party_pct counts only servers the provider publishes. Prefer the latter.
- 1 Tray.ai 89.3
- 2 Losant 83.1
- 3 Relevance AI 78.5
- 4 Automation Anywhere 75.6
- 5 Plunk 75.1
- 6 ControlUp 75
- 7 Jitterbit 74
- 8 Adobe Campaign 72
- 9 Adobe Workfront 70.3
- 10 Zapier 68.9
- 1 Zapier 66
- 2 Relevance AI 65.3
- 3 Tray.ai 62.9
- 4 FLORA 62.4
- 5 Losant 62.3
- 6 Mavenlink 61.3
- 7 Adobe Workfront 60.8
- 8 Aptly 56.3
- 9 Process Street 55.9
- 10 Nanonets 53.9
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.