Paragon · Arazzo Workflow
Paragon Verify Integration then Proxy a Request
Version 1.0.0
Confirm the Connected User has the integration enabled, then proxy a live API call to it.
View Spec
View on GitHub
Embedded IntegrationsIntegration InfrastructureiPaaSAI AgentsMCPIntegrationArazzoWorkflows
Provider
Workflows
verify-integration-and-proxy-request
Check the integration is connected, then proxy a GET to the provider.
Reads the Connected User, verifies the target integration is enabled in the project, and proxies a GET request to the integration provider only when the integration is available.
1
getUser
getUser
Read the authenticated Connected User to confirm they are authenticated and to capture their enabled integrations map.
2
getIntegrations
getIntegrations
Retrieve the project integrations and confirm at least one is enabled for the Connected User before attempting a proxied call.
3
proxyGetRequest
proxyGetRequest
Proxy a GET request to the third-party integration provider's API on behalf of the Connected User.
Source API Descriptions
openapi
Arazzo Workflow Specification
Work with this as data
Every workflow here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for arazzo workflows
4 MCP tools reach this
find_arazzoBrowse and filter every workflow in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/paragon-verify-integration-and-proxy-request-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.