Skip to main content

Make Integration

Connect OneTap Login to Make (formerly Integromat) for powerful visual automation. This guide walks you through creating scenarios that trigger when users sign in with Google.

PRO Feature

Webhooks require OneTap Login PRO. Upgrade to PRO to unlock this functionality.

Prerequisites​

  • OneTap Login PRO installed and activated
  • Make account (free tier available)
  • Basic understanding of Make concepts

Why Choose Make?​

FeatureMakeZapier
Visual builderAdvancedBasic
Operations/month (free)1,000100 tasks
Data transformationExcellentGood
ComplexityHigher learning curveEasier to start
PricingMore affordableMore expensive

Step 1: Create a Scenario​

1.1 Access Make​

  1. Go to make.com
  2. Log in or create account
  3. Click Create a new scenario

1.2 Add Webhook Module​

  1. Click the + button
  2. Search for Webhooks
  3. Select Custom webhook
  4. Click Add

Make Scenario Webhook

1.3 Create Webhook​

  1. Click Create a webhook
  2. Enter name: "OneTap Login Events"
  3. Click Save
  4. Copy the webhook URL

The URL looks like:

https://hook.us1.make.com/abc123xyz789def456

Step 2: Configure OneTap Login​

2.1 Enter Make URL​

  1. Go to WordPress Admin
  2. Navigate to Settings > OneTap Login
  3. Click Integrations tab
  4. Enable Webhooks
  5. Paste Make URL in Webhook URL
  6. Select events to trigger
  7. Click Save Changes

2.2 Send Test Data​

  1. Click Send Test Webhook
  2. Return to Make
  3. Click Run once on webhook module
  4. Make captures the data structure

Step 3: Configure Data Structure​

Automatic Detection​

Make automatically detects the JSON structure:

Make JSON Parser

Manual Data Structure​

If needed, define manually:

  1. Click webhook module
  2. Click Data structure
  3. Click Add data structure
  4. Paste sample JSON:
{
  "event": "user_registered",
  "timestamp": "2024-01-15T10:30:00Z",
  "user": {
    "id": 123,
    "email": "test@example.com",
    "first_name": "Test",
    "last_name": "User"
  }
}
  1. Click Generate

Step 4: Add Action Modules​

Example: Add to Google Sheets​

4.1 Add Google Sheets Module​

  1. Click + after webhook
  2. Search for Google Sheets
  3. Select Add a Row
  4. Connect your Google account

4.2 Configure Spreadsheet​

  1. Select your spreadsheet
  2. Select the sheet
  3. Map columns:
ColumnValue
A (Email){{1.user.email}}
B (First Name){{1.user.first_name}}
C (Last Name){{1.user.last_name}}
D (Date){{1.timestamp}}

4.3 Test Module​

  1. Click Run once
  2. Trigger a test from OneTap Login
  3. Check your Google Sheet

Step 5: Add Filters and Routers​

Filter by Event Type​

Add a filter between modules:

  1. Click the connection line
  2. Click Set up a filter
  3. Configure:
    • Label: "Only Registrations"
    • Condition: event Equal to user_registered

Router for Multiple Paths​

Add different actions for different events:

Webhook
    ↓
Router
    ↓            ↓
Path 1:         Path 2:
Registration    Login
    ↓            ↓
Sheets        Analytics
  1. Add Router module
  2. Add filter on each path
  3. Add appropriate actions

Common Make Actions​

Send to Slack​

Module: Slack > Create a Message

Configuration:

FieldValue
Channel#new-users
TextNew user: {{1.user.first_name}} ({{1.user.email}})

Create HubSpot Contact​

Module: HubSpot CRM > Create a Contact

Configuration:

FieldValue
Email{{1.user.email}}
First Name{{1.user.first_name}}
Last Name{{1.user.last_name}}
Lead SourceGoogle Sign-In

Add to Airtable​

Module: Airtable > Create a Record

Configuration:

FieldValue
BaseYour base
TableUsers
Email{{1.user.email}}
Name{{1.user.display_name}}
Registered{{1.timestamp}}

Send Email via SendGrid​

Module: SendGrid > Send an Email

Configuration:

FieldValue
To{{1.user.email}}
Fromhello@yoursite.com
SubjectWelcome to {{1.site_url}}!
ContentWelcome email HTML

Data Transformation​

Parse Timestamp​

Convert ISO timestamp to readable format:

{{formatDate(1.timestamp; "MMMM D, YYYY")}}
→ "January 15, 2024"

Extract Domain from Email​

{{last(split(1.user.email; "@"))}}
→ "gmail.com"

Conditional Text​

{{if(1.event = "user_registered"; "New User"; "Returning User")}}

Full Name Concatenation​

{{1.user.first_name}} {{1.user.last_name}}
→ "John Smith"

Advanced Scenarios​

Multi-Step Workflow​

1. Webhook: Receive OneTap event
2. Filter: Only user_registered
3. Google Sheets: Log registration
4. HTTP: Enrich with Clearbit
5. HubSpot: Create contact with enriched data
6. Slack: Notify team
7. Email: Send welcome email

Conditional Routing​

1. Webhook: Receive event
2. Router:
   Path A: If email contains @company.com
     → Slack: Notify HR team
     → Assign employee role
   Path B: If WooCommerce order_count > 0
     → Tag as returning customer
     → VIP treatment
   Path C: Default
     → Standard welcome flow

Error Handling​

Add error handler module:

  1. Click module
  2. Click Add error handler
  3. Choose handler type:
    • Ignore: Skip failed operations
    • Break: Stop scenario
    • Rollback: Undo previous actions
    • Commit: Continue despite error

Scheduling​

Instant Processing​

With webhook trigger, scenarios run instantly when data is received.

Rate Limiting​

Make respects these limits:

  • Free: 1,000 operations/month
  • Paid: Based on plan

Execution History​

View all executions:

  1. Click Scenario tab
  2. Click History
  3. Review executions, errors, data

Troubleshooting​

Webhook Not Receiving Data​

  1. Verify URL is correct in OneTap Login
  2. Check webhook is enabled
  3. Click "Run once" before sending test
  4. Check Make execution history

Data Not Mapping​

  1. Click module to inspect data
  2. Check field paths (e.g., 1.user.email)
  3. Regenerate data structure
  4. Test with fresh webhook data

Scenario Stops Running​

  1. Check for errors in history
  2. Verify connected apps still authorized
  3. Check operation limits not exceeded
  4. Ensure scenario is activated (toggle on)

Filter Blocking All​

  1. Review filter conditions
  2. Check for typos in values
  3. Test with looser conditions first
  4. Use "Run once" to debug

Best Practices​

Organization​

  • Name scenarios descriptively
  • Use notes on modules
  • Group related scenarios in folders
  • Document complex logic

Efficiency​

  • Add filters early to save operations
  • Use routers for multiple outcomes
  • Aggregate similar actions
  • Cache repeated lookups

Reliability​

  • Add error handlers
  • Set up email notifications for failures
  • Test thoroughly before activating
  • Monitor execution history weekly

Comparison with Zapier​

When to Use Make​

  • Complex multi-step workflows
  • Need visual debugging
  • Higher volume (more operations)
  • Budget-conscious

When to Use Zapier​

  • Simpler workflows
  • Faster setup needed
  • More app integrations needed
  • Team already uses Zapier

Next Steps​