Galerie AutoResources · CRM & AI assistants

Tutorial

Connect Muse, then verify your first read.

Ask Muse to create a custom connector with the Galerie Auto MCP address. Authorize access on Galerie Auto, return to Muse and verify the organization before reading inventory.

Before you begin

  • A Galerie Auto account with CRM access to the intended organization.
  • A Muse session that supports custom connectors.
  • A known vehicle in your CRM to check the first read.

Keep your Muse session open. You do not need to share a password, token or API key in the chat. The Galerie Auto screen labels below remain in French so you can identify the actual controls; this guide does not imply an English product interface. Muse labels may vary.

1. Request a connector in Muse

In your Muse conversation, ask:

Create a custom connector to the Galerie Auto MCP server at https://www.galerieauto.com/mcp. Use its native OAuth flow. Show me the connection button or link; do not ask for my password in the chat.

Open the connection button or link generated by Muse. If it only asks you to paste an API key, return to the custom connector request and check that the address ends in /mcp. Do not substitute your email address for a technical identifier.

2. Sign in and authorize on Galerie Auto

Sign in on Galerie Auto if needed. Check the domain in the address bar, application name and organization. Choose the intended organization and required permissions, then select Autoriser la connexion (authorize the connection).

Initially, only inventory, customer and calendar reads are selected, subject to your account rights. Writes and Facebook Marketplace or Messenger access are optional. Linked permissions are selected together. The consent screen covers ten permissions across five families, with reads and actions separate.

Access remains limited by the account’s rights. If the organization is missing or access is denied, check your CRM access instead of choosing another organization to finish the tutorial. See the permissions reference.

Do not save a temporary authorization URL for reuse. It belongs to a specific request. Start a fresh connection request in Muse when trying again.

3. Return to Muse and check identity

The screen Galerie Auto est prêt. (Galerie Auto is ready) confirms that authorization was recorded. Select Retourner à l’application (return to the application; the button may use Muse’s name) to continue the OAuth return. This confirmation does not prove that Muse completed the connection.

Check my Galerie Auto connection with galauto_identity, then the authorized organization with galauto_organizations. Do not change anything.

A successful check is a tool response identifying the intended organization. A completed authorization screen or a chat message saying “connected” does not replace that read. Keep identity responses out of public screenshots.

4. Read a known vehicle

Ask Muse to find the chosen vehicle, then read its record with galauto_get_vehicle. Compare stock number, recorded price and status with the CRM. If similar vehicles appear, select the correct record before continuing.

Next, you can check the returned photo links. Data access, opening an image and displaying it in Muse are three separate checks. The inventory guide explains filters and pagination.

If a step does not complete

Expired page or interrupted return
Start a fresh request in your signed-in Muse session. Do not edit OAuth URL parameters manually.
Missing tool or denied access
Check the organization and account rights. The catalogue is filtered; a missing tool alone does not prove a server fault.
Search with no results
Remove a filter and check the vehicle’s CRM status. An empty result does not by itself mean a broken connection.
Stop access
Open Applications connectées (French interface), then select Retirer l’accès (remove access). Also disconnect the connector in Muse if you no longer use it.

For symptom-specific checks, see troubleshooting (French). These steps distinguish authorization, return, reads and external actions; they do not certify a new native Muse return or any Facebook/Messenger action.

Product documentation reviewed on . Examples are requests to adapt, with no customer data or guaranteed outcome.

Additional sources: