Skip to main content

Overview

The Actions Explorer (app.stackone.com/actions) shows all available actions across your connectors. Use it to find actions, check parameters, and test them in the Playground.

Browse All Actions

View the complete catalog of actions across all integration categories

Filter & Search

Find specific actions by category, provider, or keyword

View Details

See action parameters, inputs, outputs, and descriptions

Test Instantly

Jump to the AI Playground to test any action with real data

Accessing the Actions Explorer

  1. Navigate to app.stackone.com/actions
  2. Sign in to your StackOne account
  3. Browse connectors and click on any to view its available actions
Actions Explorer interface showing integrations like Greenhouse, Ashby, HiBob, and their supported authentication methods

The Actions Explorer showing available connectors and their actions

Quick access: You can also access the Actions Explorer from the sidebar navigation in the StackOne dashboard.

Understanding Actions

Actions are the building blocks of StackOne connectors. Each action represents a specific operation you can perform with a provider, such as:
  • List operations - Retrieve collections of records (e.g., list employees, list contacts)
  • Get operations - Fetch a single record by ID
  • Create operations - Add new records to a system
  • Update operations - Modify existing records
  • Delete operations - Remove records

Action Types

Direct access to provider APIs. These actions expose the full capabilities of each integration.Examples:
  • gong_crm_search_calls - Search CRM calls in Gong
  • ashby_list_applications - List applications from Ashby ATS
  • workday_list_employees - List employees from Workday HRIS
  • salesforce_list_accounts - List accounts from Salesforce CRM
Standardized actions that work consistently across all providers in a category. Use these when you want your agent or application to work with any provider without provider-specific code.Examples:
  • iam_list_users - List users from Okta, Azure AD, Google Workspace, or any IAM provider
  • iam_list_groups - List groups across identity providers
  • documents_list_files - List files from Google Drive, SharePoint, Dropbox, or any document provider
  • documents_download_file - Download files with a consistent interface
Unified actions normalize data schemas across providers, so your code works identically regardless of which system your user connects.
Want to build unified actions for your own connectors? See the Connector Engine to create custom connectors with unified schemas.

Using the Actions Explorer

Browsing Connectors

The main page displays all available connectors in a list. Each row shows:
  • Connector name with icon and action count
  • Supported auth configs (OAuth, API Key, Basic, etc.)
  • Quick actions - Play button to test in Playground
Click on any connector row to open the details panel.

Exploring Connector Actions

After selecting a connector, a side panel opens with:
  • Search bar - Filter actions by name or keyword
  • Tags filter - Filter by action type or category
  • Auth Configs filter - Filter by authentication type
  • Use in Playground - Launch the connector directly in the AI Playground
  • MCP setup info - Ready-to-use MCP server URL and headers
  • AI Toolset docs - Link to SDK documentation
The actions table lists all available operations for the connector with their names and descriptions.
Use the Active Actions Only toggle to show only actions that are currently enabled for your account.

From Explorer to Execution

Once you’ve found an action you want to use, you have several options:

Example: Using an Action

After finding an action like workday_list_employees, here’s how you’d use it:
  1. Go to app.stackone.com/playground
  2. Select your Workday account
  3. Ask: “List all employees from Workday”
  4. The AI will automatically use the workday_list_employees action

Best Practices

Before integrating actions into your application, test them in the AI Playground to understand their behavior and outputs.
Review the required and optional parameters for each action. Some actions require specific inputs to function correctly.
Use Request Logs to monitor action executions and troubleshoot issues.