Muse workflow connector

Use this connector to start an existing SocialCRM workflow from Muse. The connector also lists available workflows, checks credits, and reads run status. It does not create or edit contacts, brands, or prompt sets.

The Muse Connector Platform accepts connectors for review. SocialCRM has not been approved or listed in Muse. A Muse account owner must complete any sign-in, consent, and submission steps.

Endpoints

The OpenAPI contract lists five workflow operations. The hosted MCP server exposes the wider SocialCRM tool catalog. Use the OpenAPI contract when you need Muse to discover only workflow operations. This contract is a discovery limit, not an authorization boundary: the current socialcrm.write OAuth scope also permits other SocialCRM write tools. Use the MCP endpoint only when Muse accepts a hosted MCP server and the wider catalog is acceptable.

Workflow operations

1. Call list_workflows to get available workflow IDs and credit costs.
2. Call get_credits to check available credits.
3. Confirm the workflow ID and expected credit cost with the user. Then call run_workflow once. A successful call returns a runId while the workflow continues in the background.
4. Call get_run_status with the returned runId until the run reaches a terminal status.
5. If the start request times out, call list_workflow_runs before you try to start the same workflow again. A second start can create a second run and consume more credits.

OAuth uses socialcrm.read for discovery and status. Starting a workflow requires socialcrm.write. An account must have access to a SocialCRM company workspace. The workflow must be available on the account's plan, and the account must have enough credits. SocialCRM applies its normal run and rate limits.

Do not put an API key in a Muse prompt. If the connection uses an API key, enter it only in Muse's credential flow. OAuth authorization and consent must be completed by the SocialCRM user.

Example requests

• “List the SocialCRM workflows I can run and show their credit costs.”
• “Check my SocialCRM credits, then start the AI Shop Checkup workflow for my brand after I confirm the cost.”
• “Show the status of SocialCRM run RUN_ID.”

Verification before submission

Check the deployed endpoints and run one authorized workflow in a test company. Confirm that Muse can discover the operations, complete authentication, start exactly one run, and read its terminal status. A public endpoint check alone does not prove account linking or a successful Muse run.

The connector listing needs a product description, example requests, support and policy links, and the endpoint or API documentation. Muse reviews submissions for functional, security, and legal requirements. Approval and directory placement are Muse decisions.

Submission details

The submitter must review the final listing and complete Muse's submission process. The OpenAPI URL and this guide will work on the public site only after deployment.