Stood CRM <> Make - Integration Guide

Connect your Stood CRM with Make to automate workflows:

• Outbound: based on deal or contact real-time events.

• Inbound: submit web form to create Account, Contact & Deal.

Stood CRM is a Make Tech Partner

🚀 Quick Start

Prerequisites

1. A Stood CRM account with admin access

2. A Make account

📋 Part 1: Credentials

Get Your Stood Credentials to setup Make

1. Cloud Functions URL

This is your Firebase Cloud Functions base URL in the format: https://REGION-PROJECTID.cloudfunctions.net

How to find it:

1. Go to Firebase Console and retrieve regions and functions deployed

2. Or from Stood → Admin → Global Settings

2. Team ID & API key

1. Go to Stood → Admin → Teams

2. Your Team ID is displayed in the team card header (e.g., zDdmpWNC5RcXSpTeklPw)

3. You can generate and copy your Webform API key from Connector section.

Security Note: Keep your API Key secret! Anyone with this key can submit forms and receive webhooks for your team.

🔌 Part 2: Connect Make.com to Stood CRM

Create Connection in Make.com

1. Open Make.com and go to your scenario

2. Add a Stood CRM module (either "Submit Web Form" or "Watch Deals" or "Watch contacts")

3. Click Create a connection

4. Fill in the connection details:

Connection Settings:

• Cloud Functions URL: https://REGION-PROJECT.cloudfunctions.net

• Team ID: Your Team ID

• Team Key (API Key): Your webForm Key

5. Click Save

The connection will be validated automatically.

📝 Part 3: Submit Web Forms

Use the "Submit Form" action module to create contacts, accounts, and deals.

Example Use Case

Automatically create a deal when:

• A new lead fills out a form on your website

• A contact is added in another system

• An e-commerce order is placed

Module Configuration

Standard Fields:

• Contact: First Name, Last Name, Email, Phone, Role, Location

• Account: Name, Location, Website, Description

• Deal: Name, Amount, Stage, Description, Solution, Closing Date, Owner

• Source Name: Track where the lead came from

Custom Fields:
Add any custom fields using the "Custom Fields" array:

• Field Path: deal.partnerKey (use dot notation: entity.fieldName)

• Value: ABC123

Example:

Custom Fields:
  [1] Field: deal.partnerKey → Value: PARTNER001
  [2] Field: deal.industry → Value: Technology
  [3] Field: account.referralSource → Value: LinkedIn

These custom fields will be stored in the respective entity's customFields object.

🔔 Part 4: Watch Deals (Webhook Trigger)

Automate workflows when deals change in Stood CRM.

Step 4.1: Activate the Webhook in Make.com

1. Create a new scenario

2. Add the Stood CRM → Watch Deals trigger module

3. Select your connection

4. Run the scenario once to activate the webhook

5. Click on the webhook module and copy the webhook URL

Example webhook URL:

https://hook.make.com/abc123def456xyz789

Step 4.2: Configure Webhook in Stood CRM

1. Go to Admin → Teams

2. Select your team flow

3. Click "Manage Stage Activities"

4. For each stage you want to monitor:

   • Webhook URL: Paste the Make.com webhook URL

5. Click Save

Step 4.3: Test the Webhook

1. Create or update a deal in the configured stage

2. Check your Make.com scenario - you should see the webhook data arrive

📊 Deal Webhook Events

Your webhook receives data when:

Webhook Payload Structure

{
  "event": "deal.stage_changed",
  "timestamp": "2025-11-03T17:42:13.000Z",
  "deal": {
    "id": "xobJk6zLknjvbsAJKZV3",
    "name": "Acme Corp - Website",
    "stage": "s1",
    "previousStage": "s0",
    "amount": 5000,
    "customFields": {
      "partnerKey": "ABC123"
    }
  },
  "account": {
    "id": "account456",
    "name": "Acme Corp",
    "website": "https://acme.com"
  },
  "primaryContact": {
    "email": "john@acme.com",
    "fullName": "John Doe"
  },
  "team": {
    "id": "teamId123",
    "name": "Sales Team"
  }
}

🔔 Part 5: Watch Contacts (Webhook Trigger)

Automate workflows when contacts change in Stood CRM.

Note: Contact webhooks are configured globally (not per team) in the Global Settings panel.

Step 5.1: Activate the Webhook in Make.com

1. Create a new scenario

2. Add the Webhooks → Custom webhook trigger module

3. Run the scenario once to activate the webhook

4. Click on the webhook module and copy the webhook URL

Example webhook URL:

https://hook.make.com/xyz789abc123def456

Step 5.2: Configure Webhook in Stood CRM

1. Go to Admin → Global Settings

2. Scroll to the Webhook Integration section

3. Enable "Push Contact Events to Webhook"

4. Enter your Webhook URL (from Step 5.1)

1. Click Save Settings

Note: These settings apply globally to all teams. All contact events will be sent to the same webhook URL.

Step 5.3: Test the Webhook

1. Create or update a contact in Stood CRM

2. Check your Make.com scenario - you should see the webhook data arrive

📊 Contact Webhook Events

Your webhook receives data when:

Contact Webhook Payload Structure

{
  "event_type": "contact.updated",
  "timestamp": "2025-11-03T17:42:13.000Z",
  "contact": {
    "id": "contact123",
    "firstName": "John",
    "lastName": "Doe",
    "email": "john@acme.com",
    "phone": "+1-555-0123",
    "role": "CEO",
    "location": "New York",
    "archived": false,
    "activations": ["VIP", "Newsletter"],
    "customFields": {
      "linkedinProfile": "https://linkedin.com/in/johndoe",
      "companySize": "50-100"
    },
    "sharingKey": null,
    "account": "account456"
  },
  "before": {
    "firstName": "John",
    "lastName": "Doe",
    "email": "john.old@acme.com",
    "phone": "+1-555-0123"
  }
}

Payload Fields:

• event_type: The type of event (contact.created, contact.updated, contact.deleted)

• timestamp: ISO 8601 timestamp of when the event occurred

• contact: Full contact data including:

  • Standard fields: id, firstName, lastName, email, phone, role, location, archived, activations, sharingKey, account

  • customFields: All custom fields defined for contacts (no prefix)

• before: (Only for contact.updated and contact.deleted) The previous state of the contact before the change

📦 Part 6: Sub-Collections Module

Overview

Sub-collections allow you to store structured, repeatable data linked to a Deal object in Stood CRM. Common use cases include:

• Orders from e-commerce platforms

• Invoices from billing systems

• Support tickets from helpdesk tools

• Subscriptions from SaaS platforms

• Quotes

Use the "Submit Sub-Collection" action module in Make.com to automatically add items to any sub-collection.

🛠️ Prerequisites

1. Sub-collection must be pre-configured in Stood CRM (Admin →Teams → Custom Fields)

2. A valid Make.com connection to Stood CRM (see Part 2)

📝 Module Configuration

Add the Module

1. In your Make.com scenario, click "+" to add a module

2. Search for Stood CRM

3. Select "Submit Sub-Collection"

Required Fields

Sub-Collection Fields

Add fields dynamically using the "Sub-Collection Fields" array:

🔧 Step-by-Step Setup

Step 6.1: Add Module to Make.com Scenario

1. Create or edit a scenario

2. Add trigger (e.g., Shopify "Watch Orders", Stripe "Watch Events")

3. Add Stood CRM → Submit Sub-Collection module

4. Select your connection

Step 6.2: Map Your Fields

Map data from your trigger to the module fields:

Example: Shopify Order

Account Name:     {{1.customer.company}} or {{1.customer.last_name}}
Sub-Collection:   orders
Source Name:      Shopify

Sub-Collection Fields:
├── orderNumber   → {{1.order_number}}
├── orderDate     → {{formatDate(1.created_at; "YYYY-MM-DD")}}
├── totalAmount   → {{1.total_price}}
├── currency      → {{1.currency}}
├── status        → {{1.financial_status}}
└── trackingUrl   → {{1.fulfillments[0].tracking_url}}

📊 Request Payload Structure

{
  "teamId": "your-team-id",
  "teamKey": "your-api-key",
  "formData": {
    "accountName": "Acme Corporation",
    "subCollectionName": "orders",
    "sourceName": "Shopify E-commerce",
    "subCollectionFields": [
      {
        "fieldName": "orderNumber",
        "fieldValue": "ORD-2024-001"
      },
      {
        "fieldName": "orderDate",
        "fieldValue": "2024-11-15"
      },
      {
        "fieldName": "totalAmount",
        "fieldValue": "1250.00"
      },
      {
        "fieldName": "status",
        "fieldValue": "paid"
      }
    ]
  }
}

✅ Response Format

Success Response:

{
  "success": true,
  "accountId": "abc123def456",
  "dealId": "xyz789ghi012",
  "subCollectionName": "orders",
  "itemId": "item123456",
  "isNewAccount": false,
  "isNewDeal": true
}

Response Fields:

💡 Use Case Examples

E-commerce: Shopify Orders

Trigger: Shopify → Watch Orders

Billing: Stripe Invoices

Trigger: Stripe → Watch Events (invoice.paid)

Support: Zendesk Tickets

Trigger: Zendesk → Watch Tickets

📋 Field Type Guidelines

Note: Empty or whitespace-only values are automatically skipped.

🐛 Troubleshooting

Connection Test Fails

• Check Team ID: Ensure it matches exactly (case-sensitive)

• Check API Key: Verify the key still exists in Stood

• Check URL: Use the correct Cloud Functions region

Webhook Returns 410 Error

• Activate the webhook: Run your Make.com scenario once

• Get fresh URL: Copy the webhook URL after running the scenario

• Check scenario status: Ensure the scenario is active

Custom Fields Not Appearing

• Format: Use dot notation: deal.fieldName, not just fieldName

• Check spelling: Field names are case-sensitive

• View in Firestore: Check the entity's customFields object

No Data Received from Webhook

• Check stage configuration: Ensure webhook is configured for the correct stage

• Verify scenario is ON: Make.com scenario must be active

• Check webhook logs: View logs in Firestore webhook_logs collection

• Test with a deal update: Trigger the webhook by changing a deal's stage

🆘 Support

Need help? Contact your Stood CRM administrator or reach out to Stood CRM support.

Happy Automating! 🎉