Rendr + Zapier Integration Guide – Rendr

Overview

The Rendr + Zapier integration allows you to connect Rendr’s delivery platform to virtually any external system using Zapier’s no-code automation builder (Zaps).

Zapier enables you to:

Trigger deliveries from forms, CRMs, ERPs, or eCommerce platforms
Automate delivery creation and quoting
Sync delivery status updates into downstream systems
Build operational workflows without writing code

Because Zapier is highly flexible, there are many ways to structure a Zap.
Rendr’s recommended approach is to use Webhooks by Zapier to call Rendr’s API directly.

This ensures:

Full control over payload structure
Support for all Rendr API endpoints
Reliable authentication
Clear debugging and error handling paths

What You’ll Need

Before starting, ensure you have:

A Zapier 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

An event occurs in an external system (e.g. new order created).
Zapier triggers a Zap.
A Webhooks by Zapier step sends a request to the Rendr API.
Rendr responds with:
- Delivery ID
- Status
- Errors (if any)
Zapier 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 Zap in Zapier

Log into Zapier.
Click Create Zap.
Choose a Trigger App (the system that starts the workflow).

Common triggers include:

Webhooks → Catch Hook
Typeform / Google Forms → New submission
HubSpot / Salesforce → New deal / record
Shopify / WooCommerce → New paid order
Google Sheets → New row

This trigger will start the delivery workflow.

Step 2 – Add Webhooks by Zapier

Click + to add an Action step.
Search for Webhooks by Zapier.
Select either:
- Custom Request (recommended for full flexibility)
- or POST (simpler for delivery creation use cases)

Step 3 – Configure Authentication

Rendr uses Basic Authentication.

In Webhooks by Zapier → Custom Request:

Method: POST
URL: https://api.rendr.delivery/<tenant_id>/deliveries

Headers:
Content-Type: application/json

Store credentials securely. Avoid hard-coding them across multiple Zaps where possible.

Step 4 – Configure the API Request

Refer to the official Rendr API documentation:
https://docs.api.rendr.delivery/

Example: Create a delivery

Method: POST
URL:
https://api.rendr.delivery/<tenant_id>/deliveries

Body Type: Raw → JSON

Example JSON payload:

{
  "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"
  }
}

Map fields from your trigger into this JSON structure according to the integration specification.

Ensure required fields match the API documentation exactly.

Error Handling

Zapier handles errors differently from Make, but you must design for failures.

Fail fast on bad responses.
If the webhook returns a non-2xx response, Zapier will mark the task as errored.

Recommended patterns:

Send an email or Slack alert to operations
Create a Jira ticket for failed deliveries
Log failed requests in Google Sheets with response details

Retry guidance:

Retry for 500 errors or temporary timeouts
Do not repeatedly retry 422 validation errors
Route validation errors to manual review

Avoid infinite retry loops.

Testing the Integration

Before going live:

Run the Zap test using sample trigger data.
Confirm:
- HTTP response returns 200
- Delivery ID is returned
- Delivery appears in the Rendr Dashboard
Submit invalid data to confirm error handling triggers correctly.

Check Zap History for detailed request and response logs.

Common Issues

401 Unauthorized
Cause: Incorrect client_id or client_secret, or improperly encoded Authorization header
Resolution: Recheck credentials and base64 encoding. Confirm tenant_id is correct.

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

Delivery not appearing in Rendr
Cause: Zap did not execute successfully
Resolution: Check Zap History and inspect the webhook response.

Zap runs but fields are blank
Cause: Incorrect field mapping from trigger
Resolution: Verify JSON field mapping and re-test.

Support & Escalation

If you need assistance:

Email: support@rendr.delivery
Implementation Partner: Your assigned Rendr onboarding contact

If you’d like, I can also generate a copy-ready Zapier Webhooks configuration specifically aligned to your tenant structure.