Skip to main content
When building a platform on StackOne, you can dynamically discover what actions are available for each linked account. This enables you to build custom UIs that adapt to each provider’s capabilities.
This guide is for platform builders creating custom interfaces that display available integrations and actions to their end-users.
Instead of hardcoding integration capabilities, query the /actions endpoint to dynamically determine what’s available.

List all available actions

Use GET /actions to retrieve action metadata:

Filter actions by context

Filter by connector, account, or action key to get relevant actions for your UI:
See the List Actions API Reference for all available filter parameters.

Understanding the response

Results are grouped by provider, with each provider containing its list of actions. The fields you’ll use: See the List Actions API Reference for the complete response schema and an example response.

Building a dynamic action UI

Here’s how to build an interface that adapts to available actions:

Execute actions via RPC

Once a user selects an action, execute it by passing the action’s id as the action field on the RPC endpoint. See RPC/HTTP for the call shape and the Actions RPC reference for all parameters and code samples.

Real-world example: integration dashboard

Actions RPC

Execute actions programmatically

List Actions API

Full API reference for actions metadata

Multi-Tenant Accounts

Segment accounts by customer

Connector Metadata

Get connector logos and branding