Connect Make (Integromat) to your Scribeless account to send handwritten mailers programmatically based on triggers set from 2000+ different integration sources.

Typical Triggers and Integrations

Deal closed
HubSpot, Pipedrive, ActiveCampaign, Copper CRM
Contact property updated
Freshworks, SugarCRM, NetSuite, Creatio
Birthday or renewal date approaching
Zoho CRM, Salesforce, Klaviyo, Yotpo
Meeting booked
Calendly, Zoho Bookings, HubSpot, Acuity Scheduling
Order placed
WooCommerce, Magento, Salesforce Commerce Cloud
Form submitted
Typeform, Fillout, Google Forms, Zoho Forms

Prerequisites

Before setting up your Make integration:

Ensure you have access from Scribeless to set up recurring campaigns (contact your commercial team if needed)
Create a template for your handwritten sends in the Scribeless platform
Set up a recurring campaign that will receive recipients from Make (initially in "Pending" status)
Generate an API key in Settings > API Keys section of your Scribeless account

Creating Your Integration

Sign up to the Scribeless platform and create your campaign
Create a recurring campaign that will start in "Pending" status
Create your scenario in Make
Start a new scenario in your Make account
Select the trigger event from an external app
Choose the app and event that will initiate your handwritten note
Add any filters or time delays as needed
Configure conditions for when notes should be sent
Choose the "HTTP" module
Select this for the API connection
Select "HTTP request"
This will allow you to connect to the Scribeless API
Configure the HTTP request with:
- Method: POST
- URL: https://platform.scribeless.co/api/recipients
- Headers: Add header X-API-Key with your API key value
Set content type to application/json
Ensure proper formatting of your request
Include recipient data in the "request content"
Add first name, last name, and address data variables within the JSON body
Send test request
Verify your integration is working correctly

Example Request Body

{
    "campaignId": "CAMPAIGN_ID",
    "data": [
        {
            "title": "",
            "firstName": "Tim",
            "lastName": "Johnson",
            "company": "Acme Inc",
            "address": {
                "address1": "17-18 Berkeley Square",
                "address2": "",
                "address3": "",
                "city": "Bristol",
                "state": "Bristol",
                "postalCode": "BS9 1NF",
                "country": "United Kingdom"
            },
            "variables": {
                "custom_field_1": "Personalized value",
                "custom_field_2": "Another custom value"
            }
        }
    ]
}

Replace CAMPAIGN_ID with the ID of your recurring campaign. This is the last segment in the URL when viewing your campaign in the platform.

Campaign Status and Workflow

When integrating Scribeless with Make, understanding the correct campaign workflow is essential:

Pending Status for Testing

New recurring campaigns start in "Pending" status. This is specifically designed for testing your integration:

You can upload recipients against pending campaigns via Make
Recipients added to pending campaigns will generate previews
These recipients will NOT be processed for printing or mailing
No charges will be incurred for recipients in pending campaigns

Use this pending status to verify your data mapping, variable replacement, and overall integration setup.

Activating Your Campaign

Once your testing is complete and you're satisfied with the integration:

Navigate to your campaign in the Scribeless platform
Activate the campaign to change its status from "Pending" to "Ready"
After activation, any new recipients added via Make will:
- Be processed for production
- Be printed and mailed according to campaign settings
- Be charged to your account

Important: There is no separate "testing mode" - the campaign status (Pending vs. Ready) determines whether recipients are processed or not.

Best Practices

Always Test with Pending Campaigns: Use the pending status for all testing before activation
Verify Address Formatting: Ensure addresses are properly formatted for the destination country
Check Variable Mapping: Preview test recipients to confirm variables are replacing correctly
Monitor Your Scenario: Regularly check for any errors or issues in your Make workflow
Create New Pending Campaigns: For testing new integrations, create new pending campaigns rather than using active ones

Troubleshooting

Recipients not appearing: Verify your API key is valid and the X-API-Key header is correctly configured
401 Unauthorized error: Check that your API key is correctly entered in the X-API-Key header
HTTP error responses: Check your JSON formatting and required fields
503 Service Unavailable: This indicates a temporary spike in API traffic; retry your request after a few minutes
Address validation errors: Ensure complete address information is being passed from your trigger
Campaign not available: Confirm you have Admin access and that the campaign exists

Need additional help? Contact our support team at [email protected]