Make (Integromat) Integration Guide for LouderLines

Connect your LouderLines account with Make (formerly Integromat) to create powerful automated workflows. Make offers more complex logic and multi-step scenarios than other platforms.

---

What You’ll Need

Before starting, make sure you have:

• A LouderLines account on selected paid plans
• A Make account (free tier includes 1,000 operations/month)
• Your LouderLines API key

---

Part 1: Getting Your LouderLines API Key

1. Log in to your LouderLines account
2. Go to Integrations in the sidebar
3. Click Create Key in the API Keys section
4. Enter a name like “My Make Integration”
5. Select Live environment
6. Click Create Key
7. Copy the key immediately – you won’t see it again!

Your key looks like: ll_live_abc123xyz...

---

Part 2: Setting Up Webhooks in Make (Receive Events)

Make receives LouderLines events through its Webhooks module.

Step 1: Create a New Scenario

1. Log in to make.com
2. Click Create a new scenario
3. Click the + button to add your first module

Step 2: Add a Webhook Trigger

1. Search for Webhooks
2. Select Custom webhook
3. Click Add
4. Give it a name like “LouderLines Events”
5. Click Save
6. Make will generate a URL like:https://hook.eu1.make.com/abc123xyz...
7. Click Copy address to clipboard

Step 3: Configure LouderLines Webhook

1. Go to LouderLines → Integrations
2. Click Add Webhook
3. Paste the Make webhook URL
4. Select your events:
   • subscriber.created
   • subscriber.unsubscribed
   • answer.published
   • custom_post.published
5. Click Create Webhook
6. Save the signing secret (for verification if needed)

Step 4: Determine Data Structure

1. Back in Make, click Redetermine data structure
2. In LouderLines, click the Test button next to your webhook
3. Make will receive the sample data and map the fields
4. Click OK when done

Step 5: Add Your Action Modules

Now connect the apps you want to automate:

1. Click the + after the webhook module
2. Search for your app (Twitter, Notion, Slack, etc.)
3. Select the action you want
4. Map the fields from the webhook data

---

Part 3: Using HTTP Module (API Requests)

For more control, use Make’s HTTP module to call the LouderLines API directly.

Setting Up an API Request

1. Add a new module
2. Search for HTTP
3. Select Make a request
4. Configure:

For GET requests (fetching data):

URL: https://www.louderlines.com/api/v1/subscribers
Method: GET
Headers:
  - Name: Authorization
    Value: Bearer ll_live_YOUR_API_KEY
  - Name: Content-Type
    Value: application/json

For POST requests (creating data):

URL: https://www.louderlines.com/api/v1/subscribers
Method: POST
Headers:
  - Name: Authorization
    Value: Bearer ll_live_YOUR_API_KEY
  - Name: Content-Type
    Value: application/json
Body type: Raw
Content type: JSON (application/json)
Request content:
{
  "email": "{{email}}",
  "first_name": "{{name}}"
}

Parse JSON Response

After an HTTP request:

1. Add a JSON module
2. Select Parse JSON
3. Connect it to your HTTP module
4. Map the Data field to the HTTP response body

---

Part 4: Example Scenarios

Scenario 1: Auto-Post to Social Media

Goal: When you publish content, automatically post to Twitter and LinkedIn.

[Webhook] → [Router] → [Twitter: Create Tweet]
                    → [LinkedIn: Create Post]

Setup:

1. Webhook module (trigger)
   • Events: answer.published, custom_post.published
2. Router module
   • Allows parallel actions
3. Twitter module
   • Message:{{data.title}} {{substring(data.content_plain; 0; 180)}}... {{data.custom_link}} {{join(data.hashtags; " ")}}
4. LinkedIn module
   • Similar configuration

---

Scenario 2: CRM Sync with Filters

Goal: Add new subscribers to HubSpot, but only if they have a name.

[Webhook] → [Filter] → [HubSpot: Create Contact]

Setup:

1. Webhook module
   • Event: subscriber.created
2. Filter (between modules)
   • Condition: data.first_name exists and is not empty
3. HubSpot module
   • Email: {{data.email}}
   • First Name: {{data.first_name}}
   • Lead Source: “LouderLines”

---

Scenario 3: Daily Subscriber Report

Goal: Every morning, get a count of new subscribers and email yourself.

[Schedule] → [HTTP: Get Subscribers] → [Aggregator] → [Email: Send]

Setup:

1. Schedule module
   • Run: Every day at 9:00 AM
2. HTTP module
   • GET https://www.louderlines.com/api/v1/subscribers?since=24h
   • Headers with your API key
3. Array Aggregator
   • Count the results
4. Email module
   • Subject: “Daily LouderLines Report”
   • Body: “You gained {{count}} new subscribers yesterday!”

---

Scenario 4: Notion Content Archive

Goal: Create a Notion page for every piece of content you publish.

[Webhook] → [Notion: Create Page]

Setup:

1. Webhook module
   • Events: answer.published, custom_post.published
2. Notion module
   • Database: Your content archive database
   • Title: {{data.title}}
   • Properties:
     • Content: {{data.content}}
     • Published: {{created_at}}
     • URL: {{data.post_url}}
     • Has Image: {{if(data.featured_image; "Yes"; "No")}}

---

Scenario 5: Bulk Import from Google Sheets

Goal: Import subscribers from a Google Sheet into LouderLines.

[Google Sheets: Watch Rows] → [HTTP: POST Subscriber] → [Google Sheets: Update Row]

Setup:

1. Google Sheets module
   • Trigger: Watch new rows
   • Columns: Email, Name
2. HTTP module
   • POST to /api/v1/subscribers
   • Body: {"email": "{{email}}", "first_name": "{{name}}"}
3. Google Sheets module
   • Update the row to mark as “Imported”

---

Part 5: Advanced Features

Using Variables

Store values for use across modules:

1. Right-click on the scenario background
2. Select Set Variable
3. Name: api_key
4. Value: Your API key

Then use {{api_key}} in any module.

Error Handling

Add error handlers for reliability:

1. Right-click on a module
2. Select Add error handler
3. Choose:
   • Resume – Continue despite errors
   • Rollback – Undo all changes
   • Commit – Save partial progress

Scheduling

Set when your scenario runs:

1. Click the clock icon
2. Options:
   • Immediately – Runs when triggered (webhooks)
   • At regular intervals – Every 5/15/30 minutes
   • Once – Single run
   • Scheduled – Specific days/times

---

Troubleshooting

“401 Unauthorized” Error

• Check your API key is correct
• Make sure to include Bearer before the key (with space)
• Verify your LouderLines plan includes API access

Webhook Not Triggering

• Verify the webhook is Active in LouderLines
• Check the URL in Make matches exactly
• Use LouderLines Test button to send sample data
• In Make, check the webhook is listening (click “Run once”)

“Connection Refused” Error

• LouderLines servers may be temporarily unavailable
• Add a Retry error handler
• Check status.louderlines.com if available

Data Not Mapping Correctly

• Re-run Redetermine data structure on your webhook
• Check field names match (case-sensitive)
• Use the DevTools module to inspect raw data

Rate Limits

• Add a Sleep module (Tools → Sleep) between requests
• Process in smaller batches
• Upgrade your LouderLines plan for higher limits

---

Best Practices

1. Start Simple – Get basic scenarios working before adding complexity
2. Use Filters – Don’t process empty or invalid data
3. Add Error Handling – Scenarios should fail gracefully
4. Test Thoroughly – Use the “Run once” feature before scheduling
5. Monitor Operations – Check your Make dashboard for failures
6. Document Your Scenarios – Add notes explaining what each does

---

Need Help?

• LouderLines Support: support@louderlines.com
• Make Help Center: make.com/en/help
• Make Community: community.make.com
• API Documentation: LouderLines → Integrations → Docs

---

Last updated: January 2025