Skip to main content
The catalog is the registry of every operation a task can perform. It is organized in a three-level hierarchy — Platforms contain Services, which contain Actions — and is fully browsable through public, unauthenticated endpoints. When you build a flow, each task names one action from the catalog and supplies parameters matching that action’s schema.

​
The hierarchy

LevelExample IDWhat it is
Platformfive9A third-party brand or provider.
Servicefive9__configuration_serviceA specific API the platform exposes.
Actionfive9__configuration_service__add_to_listA single operation on that service.
IDs follow a strict naming convention: segments joined by double underscores (__), each segment lowercase alphanumeric with single underscores. The ID encodes its own ancestry — an action ID is always platform__service__action, so five9__configuration_service__add_to_list tells you the platform (five9), the service (five9__configuration_service), and the operation (add_to_list) at a glance. A task references all three levels plus a version: 
{
  "task_id": "task_1",
  "task_name": "Add to list",
  "platform_id": "five9",
  "service_id": "five9__configuration_service",
  "action_id": "five9__configuration_service__add_to_list",
  "action_version": "1.0",
  "connection_id": "conn_e5f6g7h8",
  "parameters": { "list_name": "Outbound Q3" }
}
action_version defaults to "1.0"; actions carry a version so behavior can evolve without breaking existing flows.

​
Browsing the catalog

All catalog endpoints are read-only and require no authentication. List endpoints support status, limit (default 50), and skip query parameters.
MethodEndpointReturns
GET/catalog/platformsAll platforms.
GET/catalog/platforms/{platform_id}One platform.
GET/catalog/platforms/{platform_id}/servicesA platform’s services.
GET/catalog/services/{service_id}One service.
GET/catalog/services/{service_id}/actionsA service’s actions.
GET/catalog/actions/{action_id}One action, with its full parameter and output schemas.
curl "$BASE_URL/catalog/actions/five9__configuration_service__add_to_list"
Every catalog entry carries a status: active (usable now), coming_soon, and inactive (platforms and services) or deprecated (actions).

​
What each level tells you

Identity and discovery: name, icon, tags (e.g. contact-center, ccaas), and status. Use tags to find platforms by capability.
How the underlying API works: protocol (REST, SOAP, GraphQL, gRPC, SMTP, or WebSocket), auth_method (what kind of credentials a connection needs — basic_auth, oauth2, client_credentials, jwt, api_key, or soap_wss), base_url, and a docs_url pointing at the vendor’s own documentation.
The contract your task must satisfy: parameters, output_schema, an optional sample_output, and batching capability (batch_capable plus batch_settings such as max_records_per_call).

​
Action parameters

Each action defines its parameters as a schema — name, type, whether it’s required, and a description: 
{
  "parameters": {
    "list_name": {
      "type": "string",
      "required": true,
      "description": "Name of the target contact list"
    }
  }
}
Your task’s parameters object supplies these values, with expressions anywhere you need runtime data. The output_schema documents the fields the action returns, which downstream steps can reference as {{step_id.task_id.output.<field>}}.

​
What’s in the catalog

Five9 is the flagship platform: contact center operations against the Five9 Configuration Service, including dialing-list actions like five9__configuration_service__add_to_list. These actions require a connection with your Five9 credentials, and the list operations are batch-capable for batched delivery. GetDialed utilities (getdialed platform, getdialed__utils service) are built-in helpers that need no connection:
ActionWhat it does
getdialed__utils__echoReturns its parameters as output — handy for testing a flow’s wiring and expressions without touching an external system.
getdialed__utils__sleepWaits for duration_seconds (default 60) before completing — useful for simulating a long-running task.
The quickstart builds its first flow entirely from getdialed__utils__echo, so you can see the full trigger-to-result loop before setting up any credentials.

​
Next steps

Connections

Store credentials for the platforms your tasks call.

Flow definitions

Assemble catalog actions into steps and tasks.

Batched delivery

Use batch-capable actions for high-volume writes.

API reference

Full request and response schemas for every catalog endpoint.