A valid request URL is required to generate request examples{
"success": true,
"data": [
{
"created": true,
"skill": {
"id": "skl_9a1c4e77bd0243fb",
"agentId": "agt_4f9c2b7e10a24d51",
"organizationId": "org_2h8kqT5wLpX9",
"name": "get_contact",
"description": "Look up a HubSpot contact by email.",
"skillType": "mcp"
}
},
{
"created": false,
"skill": {
"id": "skl_3f0b18aa79c14e62",
"agentId": "agt_4f9c2b7e10a24d51",
"organizationId": "org_2h8kqT5wLpX9",
"name": "create_contact",
"description": "Create a new HubSpot contact.",
"skillType": "mcp"
}
}
]
}{
"type": "about:blank",
"title": "<string>",
"status": 123,
"detail": "<string>",
"instance": "<string>",
"code": "<string>",
"errors": [
{
"field": "<string>",
"message": "<string>"
}
]
}{
"type": "about:blank",
"title": "<string>",
"status": 123,
"detail": "<string>",
"instance": "<string>",
"code": "<string>",
"errors": [
{
"field": "<string>",
"message": "<string>"
}
]
}{
"type": "about:blank",
"title": "<string>",
"status": 123,
"detail": "<string>",
"instance": "<string>",
"code": "<string>",
"errors": [
{
"field": "<string>",
"message": "<string>"
}
]
}Add an integration's actions as skills
Turns a connected integration into ready-to-use skills on an agent: one skill per action, or every key action when none are specified. Re-running is safe, as actions that already exist as skills are skipped. Actions that still need configuration are created as disabled drafts until you complete their settings.
A valid request URL is required to generate request examples{
"success": true,
"data": [
{
"created": true,
"skill": {
"id": "skl_9a1c4e77bd0243fb",
"agentId": "agt_4f9c2b7e10a24d51",
"organizationId": "org_2h8kqT5wLpX9",
"name": "get_contact",
"description": "Look up a HubSpot contact by email.",
"skillType": "mcp"
}
},
{
"created": false,
"skill": {
"id": "skl_3f0b18aa79c14e62",
"agentId": "agt_4f9c2b7e10a24d51",
"organizationId": "org_2h8kqT5wLpX9",
"name": "create_contact",
"description": "Create a new HubSpot contact.",
"skillType": "mcp"
}
}
]
}{
"type": "about:blank",
"title": "<string>",
"status": 123,
"detail": "<string>",
"instance": "<string>",
"code": "<string>",
"errors": [
{
"field": "<string>",
"message": "<string>"
}
]
}{
"type": "about:blank",
"title": "<string>",
"status": 123,
"detail": "<string>",
"instance": "<string>",
"code": "<string>",
"errors": [
{
"field": "<string>",
"message": "<string>"
}
]
}{
"type": "about:blank",
"title": "<string>",
"status": 123,
"detail": "<string>",
"instance": "<string>",
"code": "<string>",
"errors": [
{
"field": "<string>",
"message": "<string>"
}
]
}Authorizations
Flowyte secret API key (Authorization: Bearer flowyte_sk_live_…). Scope-gated; is scoped to your organization — a key can never reach another tenant. The listed scopes in each operation's apiKey requirement are the scopes that key must hold. The tokenUrl is nominal: keys are minted in the dashboard.
- Token URL
- /api/v1/api-keys
Path Parameters
The agent this resource is scoped to (the UUID returned by createAgent / listAgents).
The integration provider (connector). One of the supported connector slugs: native providers (google_calendar, google_sheets, calendly, hubspot, ``, square, opentable, shopify), SQL databases (postgres, mysql), the universal Zapier MCP fallback (zapier), or Composio (composio).
google_calendar, google_sheets, calendly, hubspot, square, opentable, shopify, postgres, mysql, zapier, composio Body
Which actions to provision. Omit/empty to provision every important action.