Yembo Integration (Beta)

Overview: This guide covers how the Yembo AI-powered virtual survey integration works with Supermove. This is a bidirectional integration — Supermove sends project data to Yembo to initiate a virtual survey, and Yembo sends the completed survey results (inventory, notes, and move details) back into Supermove. It is intended as a reference for how the integration is configured and how data flows between both platforms.

 Relevant Links:

• Known Lead Provider Integrations — Link
• Debugging Inbound Leads — Link
• Automations on the Project Toolbar (Automation logs) - Link
• Yembo Website — Link

Overview of the Integration Workflow

The Yembo integration supports moves that originate in either Supermove or Yembo. The core workflow is as follows:

1. A project is created in Supermove (either from a lead or manually).
2. Supermove sends the project data to Yembo via an automation-triggered webhook, which creates a corresponding move record in Yembo and returns a Yembo Move Key to be stored in Supermove.
3. The customer completes a Yembo virtual survey.
4. Yembo sends the completed survey data back to Supermove via webhook, updating the project with inventory, notes, and the Yembo Move URL link. This is triggered by the Yembo move_reviewed webhook. The integration also supports moves that originate directly in Yembo, which will create a new project in Supermove when triggered. 

Steps to Enable Yembo in Supermove

Please note there are additional steps to enable this integration in Yembo. In order to enable the integration within Supermove, the following must be configured in your Supermove account:

1. Known Lead Provider Endpoint Configured — A Yembo lead provider endpoint must be provisioned in your Supermove Lead Provider Portal (this is your unique inbound webhook URL for receiving data from Yembo). Link to the Guide for Configuring this Endpoint here. 
2. Billing Variable: YEMBO_MOVE_KEY — A billing variable must be created at the project level with the name YEMBO_MOVE_KEY. This stores the Yembo Move Key returned after a project is synced to Yembo. Link to The Billing Engine (In-Depth) Guide which covers creating Billing Variables here.
3. Project Tag: YEMBO_SYNCED — A project tag named YEMBO_SYNCED must be created. This tag is applied to projects that have been successfully sent to Yembo, and is also used to prevent duplicate sends. 
4. Get Yembo Access Token — This is the token used in steps 5 and 6. The token can be generated in the Yembo Dev Center in API Tokens. Please contact your Yembo representative if you have questions on where to find this. 

5. Automation — New Project Created (Supermove → Yembo) — An automation must be set up to trigger when a new project is created, sending project data to Yembo and storing the returned Yembo Move Key. Link to the Automation Overview Guide which covers how to create a Supermove Automation here. Screenshot below of an example automation for project created:

   

6. Automation — Project Tag Added (for updates) — A second automation must be configured to trigger when the YEMBO_SYNCED tag is applied or when an update is needed, sending the Supermove Project UUID to Yembo. Link to the Automation Overview Guide which covers how to create a Supermove Automation here. Screenshot example of the automation for the project tag below:

Note: The "New Project Created" automation is configured to only send to Yembo if the project did not originate from Yembo. This prevents a circular loop where a Yembo-initiated lead triggers a duplicate send back to Yembo.

Integration Settings

Directional Syncs: 

Supermove → Yembo (Sending Project Data)

When a new project is created in Supermove (and did not originate from Yembo), an automation sends a webhook payload to Yembo's API endpoint to create a corresponding move record. Authentication: Requests to Yembo's API require a developer access token passed as a request header:

Yembo → Supermove (Receiving Survey Data)

After a Yembo virtual survey is completed and the Move is marked as Reviewed, Yembo sends a webhook payload to your Supermove lead provider endpoint. This creates or updates a project in Supermove with the survey results. The trigger in Yembo is the review of the move being compeleted. 

Note: For a new Supermove project to be created from a Yembo webhook, the following fields are required:

• person.givenName
• person.familyName
• location.streetAddress

Re-syching Data from Supermove Into Yembo (Customer or Project Details are Updated)

If a project is updated in Supermove before the Yembo move has been reviewed which triggers the final sync. You can re-trigger the automation created in step 5 of the Supermove setup process by accessing the  automations on the project toolbar in Supermove. 

Note: This must be manually done for the systems to stay in sync

What Syncs into Supermove

When Yembo sends data into Supermove, the following information is mapped into the project:

What Cannot Sync into Supermove

The following data types from Yembo are outside the scope of this integration and will not be ingested:

• File attachments (PDFs, images, videos)
• Estimate or pricing information
• Appointment information
• Tariff or billing information
• Move status changes (status management remains within Supermove)

Yembo Move Key & Project Linking

The Yembo Move Key is the primary identifier used to link a Supermove project to its corresponding Yembo move record.

• Where it lives in Supermove: Currently, the "yembo_move_key: <key here>" is stored in the project descriptions. Supermove is working to move this into the YEMBO_MOVE_KEY billing variable at the project level for use by this integration. 
• Where it comes from: Returned by Yembo's API after a project is first sent from Supermove to Yembo.
• How it's used: Yembo includes the Yembo Move Key in all subsequent webhook payloads, allowing Supermove to match incoming survey data to the correct project.
• Yembo Move URL format: https://app.yembo.ai/move/<moveKey>/overview This URL is stored in the Supermove project's office notes and on individual items in the survey and provides a direct link to the Yembo move overview for easy reference.

YEMBO_SYNCED Tag

The YEMBO_SYNCED project tag serves two purposes:

1. It visually indicates in Supermove that a project has been successfully synced with Yembo.
2. It is used by the outbound automation logic to prevent re-sending a project to Yembo if it originally came from Yembo (avoiding circular sync loops).

Debugging

If you experience issues with the integration, check the following:

• Inbound (Yembo → Supermove): Review the inbound lead logs in Supermove under the lead provider settings. Common issues include missing required fields (person.givenName, person.familyName, location.streetAddress) or webhook validation failures.
• Outbound (Supermove → Yembo): Review the automations on the project toolbar in Supermove. These are found by looking at the project page itself. Ensure the YEMBO_MOVE_KEY billing variable has been created and that the YEMBO_SYNCED tag logic is correctly configured.
• Relevant guides: Known Lead Provider Integrations, Debugging Inbound Leads, Automation Logs