Connect WarmySender to Make
Yes — WarmySender connects to Make (formerly Integromat) without a branded app, using Make's generic modules. Three shapes:
- WarmySender → Make (events): Webhooks → Custom webhook receives every reply, bounce, accepted LinkedIn invite and more — the steps below.
- Make → WarmySender (actions): HTTP → Make a request calls the REST API. Add a header Authorization: Bearer ws_… (your API key from Settings → API Keys) and, for example, POST https://warmysender.com/api/v1/prospects with a JSON body containing email plus enrollInCampaignId to save a lead and enroll them in one step. Every call is in the API reference at /docs/integrations.
- AI agent: if your Make plan's AI agent can connect to an MCP server, point it at https://warmysender.com/mcp with the same key; otherwise let it call the REST API. Either way the agent never sends a message itself and can never raise a limit — the scheduler paces everything.
Included on every paid WarmySender plan, including the AppSumo lifetime tiers.
Why Make:
Make offers more complex branching, filtering, and data transformation than Zapier — ideal for multi-step automation with conditional logic.
Step-by-Step Setup:
Step 1: Create a new Scenario in Make
• Log in to make.com and click 'Create a new Scenario'.
• Add a trigger module: search for 'Webhooks' and select 'Custom webhook'.
• Click 'Add' to create a new webhook — Make generates a unique URL. Copy it.
Step 2: Register in WarmySender
• Go to Settings > Webhooks > Create Webhook.
• Paste the Make webhook URL.
• Subscribe to your desired events.
• Click 'Test' to send a sample event.
Step 3: Determine data structure
• Go back to Make and click 'Redetermine data structure' on the webhook module.
• It will detect the WarmySender payload fields automatically.
Step 4: Add action modules
Connect modules for your destination app:
• Router module — Branch based on event type (reply.received → one path, email.bounced → another).
• HubSpot module — Create/Update Contact, Create Deal.
• Google Sheets module — Add Row.
• Slack module — Send Message.
• HTTP module — Call any API.
Step 5: Add filters and routing
Make excels at conditional routing:
• Route 1: If type = 'reply.received' → Create CRM deal + Notify Slack
• Route 2: If type = 'email.bounced' → Update CRM status + Log to sheet
• Route 3: If type = 'email.clicked' → Score lead + Create task
Step 6: Enable the scenario
Set the scheduling to 'Immediately' (webhook-triggered). Toggle the scenario on.
Advanced Features:
- Data stores — Keep a local database in Make for deduplication and lookups.
- Iterators — Process multiple items from a single webhook (e.g., batch events).
- Error handlers — Add fallback routes for failed operations.
- Aggregators — Collect multiple events and send a daily summary.
Best Practices:
- Use Make's built-in 'JSON' module to parse the webhook payload if auto-detection fails.
- Add error handlers to every critical module to prevent scenario failures.
- Use data stores to track which prospects have already been synced to avoid duplicates.
- Set up email notifications for scenario errors in Make's settings.