Make (Integromat) Integration

Connect Orsa to Make's visual automation platform for powerful brand enrichment workflows with branching logic, iterators, and data transformations.

Getting Started

1. Add Orsa as an HTTP Module

Make doesn't have a native Orsa app yet. Use the HTTP module to call the API directly.

1. Add an HTTP → Make a Request module to your scenario
2. Set the URL to https://api.orsa.dev/v1/brand/retrieve
3. Add a header: Authorization: Bearer YOUR_API_KEY
4. Set method to GET
5. Add query parameters as needed

2. Create a Reusable Connection

Set up a custom connection to avoid repeating auth headers:

1. Go to Connections → Create a connection
2. Type: HTTP with API Key
3. Header name: Authorization
4. Header value: Bearer YOUR_API_KEY
5. Save and reuse across all Orsa modules

Example Scenario: Lead Enrichment Pipeline

Webhook → HTTP (Orsa Brand) → Router → CRM Update
  ↓                              ↓
 email: ceo@stripe.com      Branch 1: Brand found → Update CRM
                             Branch 2: Not found → Flag for review

Module 1: Trigger

Use a Webhook or CRM trigger (new contact, new deal, etc.)

Module 2: Orsa Brand Lookup

Module: HTTP → Make a Request
Method: GET
URL: https://api.orsa.dev/v1/brand/retrieve-by-email
Query: email = {{1.email}}
Headers: Authorization = Bearer {{connection.apiKey}}
Parse Response: Yes

Module 3: Router

• Route 1: Filter where success equals true → Update CRM with brand data
• Route 2: Filter where success equals false → Add to manual review queue

Module 4: CRM Update

Map Orsa fields to your CRM:

Company Name: {{2.data.name}}
Website: https://{{2.data.domain}}
Industry: {{2.data.industry}}
Logo URL: {{2.data.logos[1].url}}

Batch Processing with Iterators

Process a list of domains from a spreadsheet:

Google Sheets (Get Rows) → Iterator → HTTP (Orsa) → Google Sheets (Update Row)

Add a Sleep module (1 second) between iterations to respect rate limits.

Available Endpoints

Error Handling

Use Make's Error Handler module to catch failures:

• Resume: Skip failed items and continue the scenario
• Rollback: Undo previous actions if Orsa fails
• Break: Stop and retry the failed module later

Filter for specific error codes:

{{2.error.code}} = "RATE_LIMITED" → Sleep 30s → Retry
{{2.error.code}} = "NOT_FOUND" → Log and skip

Tips

• Enable "Parse Response" on HTTP modules to access JSON fields directly in subsequent modules.
• Use the Sleep module between batch calls to avoid rate limits (1-2 seconds between requests).
• Store results in a Data Store to avoid re-fetching the same domains.
• Use Router filters to handle different response scenarios (found, not found, error) gracefully.