Skip to main content
MindStudio
Pricing
Blog About
My Workspace
Utilities

Run Connector from MindStudio Connector Registry (MSCR)

The Run Connector from MindStudio Connector Registry (MSCR) block executes a raw API connector to a third-party service using a pre-defined action from the MindStudio Connector Registry.

Run third-party API connectors from the MindStudio registry

The Run Connector from MindStudio Connector Registry (MSCR) block executes a raw API connector to a third-party service using a pre-defined action from the MindStudio Connector Registry. It acts as a bridge between your workflow and external services, letting you invoke specific service actions without manually constructing HTTP requests. The block is configured with an action identifier in the format serviceId/actionId (for example, slack/send-message), a display name, an icon, and a set of configuration values that supply the required inputs for that action.

The block accepts an optional connection ID to authenticate requests through a specific OAuth connection. If no connection ID is provided, the block falls back to the default connection configured for that service. Configuration values are passed as a key-value map, where the keys correspond to the input parameters defined by the selected action in the registry.

This block fits into workflows that need to interact with external platforms and services — such as sending notifications, reading or writing data to SaaS tools, or triggering actions in connected applications. Because it draws from the MindStudio Connector Registry, it can be used with any service and action available in that registry, making it a general-purpose integration block within utility-focused workflows.

What you can build

Real-world workflows powered by the Run Connector from MindStudio Connector Registry (MSCR) block.

Send Slack Notifications

Trigger a Slack message action from within a workflow to notify a channel when a specific condition or event occurs.

Write Data to CRM

Invoke a CRM service action to create or update contact records based on data collected earlier in the workflow.

Fetch External API Data

Call a registered third-party service action to retrieve data and pass the response into downstream workflow blocks.

Trigger Project Management Tasks

Use a connector action to create tasks or update project records in tools like Asana or Jira from within an automated workflow.

Post to Social Platforms

Execute a social media service action to publish content or updates to a connected platform account.

Authenticate with OAuth Services

Pass a specific OAuth connection ID to authenticate requests to services that require user-level credentials, enabling multi-user workflows.

Ready to add Run Connector from MindStudio Connector Registry (MSCR) to your workflow?

Get Started Free

Common questions about Run Connector from MindStudio Connector Registry (MSCR)

What parameters are required to configure this block?

The block requires an actionId in the format serviceId/actionId (for example, slack/send-message), a displayName, an icon, and a configurationValues map containing the key-value pairs that correspond to the selected action's input parameters. An optional __connectionId can be provided to specify which OAuth connection to use for authentication.

What does this block return as output?

The block metadata does not define a structured output schema. The response returned will depend on the specific third-party service action being invoked. You can inspect the action's expected response by consulting the /developer/v2/helpers/connectors/{serviceId}/{actionId} endpoint.

How do I know which services and actions are available?

You can retrieve a list of available services and actions from the MindStudio Connector Registry using the /developer/v2/helpers/connectors endpoint. To get the full input configuration for a specific action, use /developer/v2/helpers/connectors/{serviceId}/{actionId}.

How does authentication work with this block?

Authentication is handled via OAuth connections. You can pass a __connectionId to specify a particular OAuth connection. If no connection ID is provided, the block uses the default connection configured for that service, if one exists.

What kinds of workflows commonly use this block?

This block is used in workflows that need to interact with external SaaS platforms or APIs — such as sending messages, reading or writing records in third-party tools, or triggering actions in connected services. It is categorized as a Utilities block and serves as a general-purpose integration point within MindStudio workflows.

Add Run Connector from MindStudio Connector Registry (MSCR) to your workflow

Build powerful AI workflows with drag-and-drop blocks. No coding required.