Automating your workflows with Metrikia webhooks

Why automate with webhooks?

Metrikia webhooks let you create automations that react in real time to your business events. Instead of manually checking your data every day, let machines work for you.

Popular automation examples:

• Slack notification when a deal > 5,000 EUR is won
• Automatic welcome email when a new lead arrives from Meta
• Google Sheet update with daily performance metrics
• Asana/Trello task creation when a lead is qualified
• Bidirectional sync with Systeme.io for online courses
• SMS alert when an ADS sync fails

Prerequisites

• A Metrikia account with at least one active integration
• An account on your automation platform of choice (Zapier, Make, n8n, or other)
• Metrikia webhooks configured (see the "Configure webhooks" guide)

Automation 1: Slack "Deal won" notification

Goal: Receive an automatic Slack message with details when a deal is won.

With Zapier

1. Trigger: Webhooks by Zapier > Catch Hook
2. Copy the webhook URL into Metrikia (event deal.won)
3. Test: Mark a deal as won in Metrikia, verify Zapier receives the event
4. Action: Slack > Send Channel Message
5. Configure the message with payload variables:
   • Channel: #sales
   • Message: "Deal won! {data.title}, {data.amount} EUR by {data.leadName} (source: {data.source})"
6. Enable the Zap

With Make

1. Create a scenario with Webhooks > Custom webhook
2. Copy the URL into Metrikia (event deal.won)
3. Run a test so Make detects the structure
4. Add a Slack > Create a Message module
5. Map webhook fields to message variables
6. Activate the scenario

With n8n

1. Add a Webhook node (method: POST)
2. Copy the URL into Metrikia
3. Add a Slack > Send Message node
4. Configure field mapping
5. Activate the workflow

Automation 2: Unsupported CRM sync

Goal: Automatically sync new Metrikia leads to a CRM not natively supported (e.g., Pipedrive, Close.io, or an internal tool).

Architecture

Metrikia (webhook lead.created) > Make/Zapier/n8n > Transform > Target CRM API

Detailed steps with Make

1. Webhook: Configure the Metrikia webhook with the lead.created event
2. Router (optional): Filter leads by source if you only want to sync certain sources
3. HTTP Module: Call your target CRM's API
   • Method: POST
   • URL: your CRM's lead creation endpoint
   • Headers: your CRM's authentication
   • Body: map Metrikia fields to your CRM's fields
4. Error handler: Configure an email notification on failure

Typical field mapping

Automation 3: Automatic Google Sheets reporting

Goal: Automatically populate a Google Sheet with your daily performance metrics.

With Zapier

1. Trigger: Schedule by Zapier > Every Day (9am)
2. Action 1: Webhooks by Zapier > GET > https://api.metrikia.io/api/v1/performance?dateFrom=YESTERDAY&dateTo=YESTERDAY&platform=all
   • Headers: Authorization: Bearer YOUR_KEY
3. Action 2: Google Sheets > Create Spreadsheet Row
   • Map fields: date, spend, leads, revenue, CPL, CPA, ROAS
4. Enable the Zap

Pro tip: Combine this automation with conditional formatting in Google Sheets (ROAS < 2x in red, > 4x in green) for automatic visual reporting.

Automation 4: Systeme.io integration

Goal: Sync Metrikia leads to Systeme.io to trigger automatic email sequences.

Architecture

Metrikia (lead.created) > Zapier/Make > Systeme.io API > Email sequence

Steps with Zapier

1. Trigger: Webhooks by Zapier > Catch Hook (event lead.created)
2. Filter: Continue only if source = meta or google (filter organic traffic)
3. Action: Systeme.io > Add Contact
   • Email: {data.email}
   • First name: {data.firstName}
   • Tag: "lead-metrikia-{data.source}"
4. The contact automatically enters your Systeme.io email sequence

Automation 5: Performance alerts

Goal: Receive an alert when a KPI exceeds a critical threshold.

With n8n (self-hosted)

1. Cron node: Every hour
2. HTTP Request node: GET /api/v1/performance (last 24h)
3. IF node: ROAS < 1.0?
4. Slack node (true branch): "ALERT: ROAS below 1x over the last 24h ({roas}x). Check your campaigns immediately."
5. NoOp node (false branch): Do nothing

Recommended thresholds

Best practices for your automations

1. Always test in sandbox before activating in production
2. Handle errors: Configure notifications for automation failures
3. Document your workflows: Clearly name each step
4. Limit actions: Avoid infinite loops (Metrikia > CRM > webhook > Metrikia)
5. Monitor costs: Zapier and Make charge per task, optimize your filters
6. Secure your secrets: Store API keys in environment variables, not hardcoded in workflows

Pro tip: n8n is free when self-hosted and particularly powerful for complex automations. If you are technical, it is the best option for intensive use without recurring costs.