Rendr + Make Integration Guide

Overview

The Rendr + Make integration allows you to connect Rendr’s delivery platform to virtually any external system using Make’s no-code workflow builder.

Make (formerly Integromat) enables you to:

• Trigger deliveries from forms, CRMs, ERPs, or eCommerce platforms

• Automate delivery creation

• Sync delivery status updates

• Build custom operational workflows without writing code

Because Make is highly flexible, there are many ways to structure a scenario.
Rendr’s recommended approach is to use the HTTP module for direct API communication.

This ensures:

• Full control over payload structure

• Support for all Rendr API endpoints

• Reliable authentication

• Clear error handling

---

What You’ll Need

Before starting, ensure you have:

• A Make account

• A Rendr account

• Rendr API credentials:

  • client_id

  • client_secret

• Access to the Rendr API documentation:
  https://docs.api.rendr.delivery/

• A trigger source (e.g. webhook, form, CRM event)

---

How It Works

1. An event occurs in an external system (e.g. new order created).

2. Make triggers a scenario.

3. The HTTP module sends a request to the Rendr API.

4. Rendr responds with:

   • Delivery ID

   • Status

   • Errors (if any)

5. Make continues the workflow based on the response.

You can use this integration to:

• Create deliveries

• Retrieve quotes

• Track delivery status

• Update deliveries

• Cancel deliveries

---

Installation & Configuration Steps

---

Step 1 – Create a New Scenario in Make

1. Log into Make.

2. Click Create a new scenario.

3. Select a trigger module.

Common triggers include:

• Webhooks → Custom Webhook

• Forms → Form Submission

• CRM → New Record

• Google Sheets → New Row

This trigger will start the delivery workflow.

---

Step 2 – Add the HTTP Module

1. Click the + icon after your trigger.

2. Search for HTTP.

3. Select Make a request.

This module will communicate directly with Rendr’s API.

---

Step 3 – Configure Authentication

Rendr uses Basic Authentication.

Inside the HTTP module:

1. Set Authentication to:

   • Basic Auth

2. Click Add

3. Enter the credentials provided by Rendr:

client_id: <RENDR_CLIENT_ID>
client_secret: <RENDR_CLIENT_SECRET>

Save this in Make’s keychain for secure reuse.

Do not hard-code credentials directly into headers.

---

Step 4 – Configure the API Request

Refer to the official Rendr API documentation:

https://docs.api.rendr.delivery/

For example, to create a delivery:

• Method: POST

• URL:

  https://api.rendr.delivery/tenant_id/deliveries

• Headers:

  Content-Type: application/json

• Body Type:

  Raw → JSON

Map your trigger data into the JSON payload according to the integration specification.

Example structure:

   "store_id": "rendr-test",
    "reference": "123456",
    "special_instructions": "Leave at front door",
    "pickup_instructions": "Collect from reception",
    "book_delivery_now": true,
    "use_dynamic_RFP": true,
    "delivery_type": "fast",
    "authority_to_leave":true,
    "address": {
        "business": true,
        "address": "7 Howard Street",
        "address2": "Level 3",
        "city": "Richmond",
        "state": "VIC",
        "post_code": "3121",
        "company_name": "Sample Company",
        "country":"AU"
    },

Ensure required fields match the API documentation exactly.

---

Error Handling (Critical)

Error handling must always be configured.

Without this, failed deliveries may silently break your workflow.

---

Step 1 – Enable Error Handling in Make

1. Click the HTTP module.

2. Select Add error handler.

3. Choose one of the following patterns:

Recommended:

• Break – stops the scenario and logs the error

---

Step 2 – Handle API Errors

Rendr may return:

Status Code	Meaning
200	Success
400	Validation error
401	Authentication error
422	Field validation failed
500	Server error

---

Step 3 – Optional Retry Logic

You may configure:

• Automatic retry for 500 errors

• Notification for 422 validation errors

• Manual review workflow

Avoid infinite retries.

---

Testing the Integration

Before going live:

1. Run the scenario manually.

2. Trigger a test event.

3. Confirm:

   • HTTP request returns 200

   • Delivery ID is returned

   • Delivery appears in the Rendr Dashboard

4. Confirm error handling works by:

   • Submitting invalid data

   • Confirming the scenario logs an error

---

Common Issues

---

Issue: 401 Unauthorized

Cause: Incorrect API credentials
Resolution: Re-enter Basic Auth credentials in the HTTP module

---

Issue: 422 Validation Error

Cause: Missing or invalid field in request body
Resolution: Compare payload against API documentation and correct required fields

---

Issue: Delivery not appearing in Rendr

Cause: Scenario did not execute successfully
Resolution: Check scenario history and HTTP response logs

---

Issue: Scenario runs but no data mapped

Cause: Incorrect field mapping from trigger
Resolution: Verify mapping inside JSON body

---

Support & Escalation

If you need assistance, contact Rendr Support.

Support contact:

• Email: [e-mail]

• Implementation Partner: Your assigned Rendr onboarding contact