This guide is for platform builders creating custom interfaces that display available integrations and actions to their end-users.
/actions endpoint to dynamically determine what’s available.
List all available actions
UseGET /actions to retrieve action metadata:
- TypeScript SDK
- cURL
- Python
Filter actions by context
Filter by connector, account, or action key to get relevant actions for your UI:- TypeScript SDK
- cURL
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:- TypeScript SDK
- Python
Execute actions via RPC
Once a user selects an action, execute it by passing the action’sid as the action field on the RPC endpoint. See HTTP (RPC) for the call shape and the Actions RPC reference for all parameters and code samples.
Real-world example: integration dashboard
Related
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