DocsMake (Integromat) Guide

Visual Automation Scenario Guide

Automate Client Provisioning with Make

Build modular, multi-step visual workflows with Make (formerly Integromat). Trigger scenario execution from incoming webhooks, CRM stage changes, or client onboarding forms, and configure an HTTP module to automatically provision isolated client sub-accounts and queue physical NFC countertop stands.

Scenario Workflow Architecture

Here is how your Make scenario executes client onboarding from trigger to delivery:

Module 1: Trigger

Event Ingestion

Custom Webhook, Stripe invoice, or Typeform submission.

Module 2: HTTP

Make a Request

POST payload to Aevloc with Bearer auth & 5 shipping fields.

Module 3: Aevloc

Instant Deployment

Generates review funnel & queues physical stand dispatch.

Module 4: Handoff

Client Delivery

Emails live review link & updates CRM database.

Prerequisites

An active Aevloc Agency Pro or Scale subscription (includes up to 100 client sub-accounts).

An Agency Bearer API Key (begins with aev_live_), generated inside your API & Webhooks dashboard.

A Make (Integromat) account with permissions to build scenarios using the built-in HTTP app.

Create Your Scenario Trigger

In Make, click Create a new scenario and select your starting trigger module:

Webhooks → Custom Webhook: Receive instantaneous JSON payloads from your custom checkout portal, Stripe payment webhooks, or onboarding funnel.
Typeform / Jotform / Tally: Watch for new form submissions containing business information and physical delivery addresses.
Stripe → Watch Events: Listen for checkout.session.completed or invoice payments.
Airtable / Notion / Google Sheets: Trigger when a row status changes to "Provision Client".

Delivery Data Requirement: Ensure your trigger captures the client business name, email, and the 5 physical shipping fields (Recipient Name, Street Address, City, State, and ZIP) so Aevloc can queue the physical stand without manual intervention.

Add and Configure the HTTP → Make a Request Module

Click the plus icon to add the next module, search for HTTP, and choose Make a request. Configure each field exactly as follows:

URL

https://aevloc.com/api/v1/agency/subaccounts

Method

POST

Headers (Enter 2 Items)

Name: AuthorizationValue: Bearer YOUR_API_KEY

Name: Content-TypeValue: application/json

Body Type

Raw

Content Type

JSON (application/json)

Parse Response

Yes

Map the Request Content

In the Request content field, enter the JSON payload below. Map Make's dynamic pill variables from your trigger module into each field:

Make HTTP Request Content (JSON)

{
  "name": "{{1.businessName}}",
  "adminEmail": "{{1.ownerEmail}}",
  "shippingName": "{{1.businessName}} (Attn: Front Counter)",
  "shippingAddress": "{{1.addressLine1}}",
  "shippingCity": "{{1.city}}",
  "shippingState": "{{1.state}}",
  "shippingZip": "{{1.zipCode}}"
}

Make Payload Field Specifications

JSON Key	Required	Description
name	Yes	Client business or organization name.
adminEmail	Yes	Client owner email for magic link access.
shippingName	Yes	Recipient name or storefront attention line.
shippingAddress	Yes	Physical street address including suite/unit.
shippingCity	Yes	Physical destination city.
shippingState	Yes	State or province code (e.g. "CA", "NY").
shippingZip	Yes	Postal or ZIP code.
googleReviewUrl	Optional	Direct Google review URL for high-sentiment routing.

Execute Test & Inspect Parsed Output

Click Run once at the bottom of the scenario canvas. When the HTTP module runs, Aevloc returns HTTP 201 Created with the sub-account metadata parsed into actionable Make variables:

Parsed Make Response Output (HTTP 201)

{
  "success": true,
  "data": {
    "organizationId": "0191f6a2-8b4e-7210-9831-e6e8c1a892b1",
    "name": "Beacon Bistro",
    "slug": "beacon-bistro",
    "funnelUrl": "https://aevloc.com/review?org=0191f6a2-8b4e-7210-9831-e6e8c1a892b1",
    "hardwareOrder": {
      "id": "0191f6a2-8b51-789a-bc32-11449900aabb",
      "type": "initial",
      "status": "pending",
      "recipient": "Beacon Bistro (Attn: Front Counter)"
    }
  }
}

Direct Access to Data Bundle:

Because Parse response was set to Yes, Make unpacks data.funnelUrl, data.organizationId, and data.hardwareOrder.id as native pills for all subsequent modules.

Connect Downstream Modules

Attach follow-up actions to complete the client onboarding lifecycle:

Send Welcome Email (Gmail / SendGrid)

Dispatch an email to the business owner containing their active review funnel URL ({{2.data.funnelUrl}}) and confirmation that their physical countertop stand has been queued.

Update Record (Airtable / HubSpot)

Record the generated {{2.data.organizationId}} back to the client row and change status to "Active Funnel".

Make Troubleshooting & Tips

401 Unauthorized:

Ensure the header name is Authorization and the value is Bearer aev_live_... with exactly one space. Confirm your key is active in /admin/api.

422 Unprocessable Entity:

One of the required attributes is empty. Ensure your trigger feeds valid non-empty strings for all 5 delivery fields: shippingName, shippingAddress, shippingCity, shippingState, and shippingZip.

Malformed JSON syntax:

If client names or addresses contain special characters, Make will escape them automatically in raw JSON mode if you enclose variable pills inside double quotes: "name": "{{1.businessName}}".

← Zapier Guide n8n Guide →