# API Reference
Source: https://docs.whatsable.app/api-reference/introduction

Whatsable API documentation — RESTful APIs for WhatsApp messaging. Choose Whatsable or Notifyer System.

<Info>
  Build WhatsApp-powered workflows with Whatsable's suite of APIs. Whether you're a developer integrating via REST or a business user connecting through Zapier, Make, or n8n — we've got you covered.
</Info>

## Choose your API

Select the Whatsable product that matches your use case. Each API has distinct capabilities and authentication.

### Whatsable

<div>
  <img alt="Whatsable" />

  <p>
    Internal team messaging and business alerts. Unlimited WhatsApp messages with Zapier and Make integration.
  </p>
</div>

<CardGroup>
  <Card title="Send a WhatsApp message" href="/api-reference/whatsable/messages/send-message">
    <div>
      <Badge>POST</Badge>
      <span>Send WhatsApp messages with optional attachments</span>
    </div>
  </Card>
</CardGroup>

### Notifyer System

<div>
  <img alt="Notifyer System" />

  <p>
    Full business messaging platform with real-time chat, brand messaging, and two-way communication.
  </p>
</div>

<CardGroup>
  <Card title="Get Templates" href="/api-reference/notifier-system/templates/get-templates">
    <div>
      <Badge>GET</Badge>
      <span>Retrieve all templates for your account</span>
    </div>
  </Card>

  <Card title="Send Template Message" href="/api-reference/notifier-system/templates/send-template-message">
    <div>
      <Badge>POST</Badge>
      <span>Send template-based messages to users</span>
    </div>
  </Card>
</CardGroup>

## Why Whatsable

<CardGroup>
  <Card title="Meta-Approved" icon="shield-check">
    Official WhatsApp Business API integration backed by Meta's technology partner approval.
  </Card>

  <Card title="Instant Automation" icon="zap">
    Send customized messages in real-time with webhooks and event-driven workflows.
  </Card>

  <Card title="Developer & No-Code" icon="code">
    REST APIs for custom integrations, plus ready-made connectors for Zapier, Make, and n8n.
  </Card>

  <Card title="Business Communication" icon="send">
    Alerts, confirmations, reminders, and team updates — all over WhatsApp.
  </Card>
</CardGroup>

## Connect your way

Integrate through no-code automation platforms or call our APIs directly.

<CardGroup>
  <Card title="Zapier" icon="bolt">
    Connect 6,000+ apps with pre-built Zaps. No coding required.

    <div>
      <a href="/guides/whatsable/zapier">Whatsable</a>
      <span>·</span>

      <a href="/guides/notifyer-system/zapier-overview">Notifyer System</a>
    </div>
  </Card>

  <Card title="Make" icon="lines-leaning">
    Build visual automation scenarios with drag-and-drop workflows.

    <div>
      <a href="/guides/whatsable/make">Whatsable</a>
      <span>·</span>

      <a href="/guides/notifyer-system/make-overview">Notifyer System</a>
    </div>
  </Card>

  <Card title="n8n" icon="diagram-project">
    Self-hosted or cloud workflows with full control over your automation.

    <div>
      <a href="/guides/whatsable/n8n">Whatsable</a>
      <span>·</span>

      <a href="/guides/notifyer-system/n8n-overview">Notifyer System</a>
    </div>
  </Card>

  <Card title="Direct API" icon="code">
    RESTful endpoints with API keys. Full programmatic access for custom integrations.

    <div>
      <a href="/api-reference/whatsable">Whatsable</a>
      <span>·</span>

      <a href="/api-reference/notifier-system">Notifyer System</a>
    </div>
  </Card>
</CardGroup>

## Get started

<Steps>
  <Step title="Pick your solution">
    Choose [Whatsable](https://dashboard.whatsable.app/signup) or [Notifyer System](https://console.notifyer-systems.com/) based on your messaging needs.
  </Step>

  <Step title="Authenticate">
    Get your API key from the dashboard. See [Authentication](/authentication) for header format and request examples.
  </Step>

  <Step title="Integrate">
    Use our API endpoints or follow the Zapier, Make, or n8n guides for no-code setup.
  </Step>
</Steps>

<Warning>
  **Security:** Never expose API keys in client-side code or public repositories. Use environment variables and server-side requests only.
</Warning>


# Get Templates
Source: https://docs.whatsable.app/api-reference/notifier-system/templates/get-templates

/openapi/notifier-system-api.json get /api:AFRA_QCy/get_templates
Retrieve a list of all templates associated with your account



# Send Template Message
Source: https://docs.whatsable.app/api-reference/notifier-system/templates/send-template-message

/openapi/notifier-system-api.json post /api:hFrjh8a1/send_template_message_by_api
Send a template-based message to users via their phone numbers



# Send a WhatsApp message
Source: https://docs.whatsable.app/api-reference/whatsable/messages/send-a-whatsapp-message

/openapi/whatsable-api.json post /send
Send a WhatsApp message with optional attachments (images, videos, documents)



# Authentication
Source: https://docs.whatsable.app/authentication

Authenticate with Whatsable APIs using API keys, Bearer tokens, and request headers.

# Authentication

All Whatsable APIs require authentication using API keys. This guide explains how to authenticate your requests.

## API Keys

Each API solution uses a different authentication method:

### Whatsable API

Uses an API key in the `X-API-Key` header:

```bash theme={null}
curl -X POST https://api.whatsable.app/v1/messages \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"to": "+1234567890", "message": "Hello!"}'
```

### Notifyer System

Uses a Bearer token in the Authorization header:

```bash theme={null}
curl -X POST https://api.insightssystem.com/api:hFrjh8a1/send_template_message_by_api \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"template": "template_id", "variables": {}, "phone_number": "+1234567890"}'
```

## Getting Your API Keys

1. Log in to your Whatsable dashboard
2. Navigate to the API section
3. Generate a new API key or token
4. Store it securely - it won't be shown again!

## Security Best Practices

* Never share your API keys
* Use environment variables to store keys
* Rotate keys periodically
* Use HTTPS for all API requests
* Implement proper error handling


# Error Handling
Source: https://docs.whatsable.app/guides/error-handling

Handle errors when using Whatsable APIs: HTTP status codes, error format, and retry strategies.

# Error Handling

This guide explains how to handle errors when using Whatsable APIs.

## HTTP Status Codes

All Whatsable APIs use standard HTTP status codes:

* `200 OK`: Request successful
* `400 Bad Request`: Invalid request parameters
* `401 Unauthorized`: Invalid or missing API key
* `403 Forbidden`: Insufficient permissions
* `404 Not Found`: Resource not found
* `429 Too Many Requests`: Rate limit exceeded
* `500 Internal Server Error`: Server-side error

## Error Response Format

All error responses follow this format:

```json theme={null}
{
  "error": {
    "code": "error_code",
    "message": "Human-readable error message"
  }
}
```

## Common Error Codes

### Authentication Errors

* `invalid_api_key`: API key is invalid or expired
* `missing_api_key`: API key is missing from request

### Request Errors

* `invalid_phone_number`: Phone number format is incorrect
* `invalid_template`: Template ID is invalid or not found
* `missing_required_field`: Required field is missing
* `invalid_variables`: Template variables are invalid

### Rate Limit Errors

* `rate_limit_exceeded`: Too many requests in a time period
* `quota_exceeded`: Monthly quota exceeded

## Best Practices

1. **Always Check Status Codes**: Don't assume success
2. **Implement Retry Logic**: For 429 and 500 errors
3. **Log Errors**: For debugging and monitoring
4. **Handle Timeouts**: Set appropriate timeout values
5. **Validate Input**: Before making API calls

## Example Error Handling

```javascript theme={null}
async function sendMessage() {
  try {
    const response = await fetch('https://api.insightssystem.com/api:hFrjh8a1/send_template_message_by_api', {
      method: 'POST',
      headers: {
        'Content-Type': 'application/json',
        'Authorization': 'Bearer YOUR_TOKEN'
      },
      body: JSON.stringify({
        template: 'template_id',
        variables: {},
        phone_number: '+1234567890'
      })
    });

    if (!response.ok) {
      const error = await response.json();
      throw new Error(error.error.message);
    }

    const data = await response.json();
    return data;
  } catch (error) {
    console.error('Error sending message:', error);
    // Handle error appropriately
  }
}
```


# Embedding Process
Source: https://docs.whatsable.app/guides/notifier-system/embedding-process

Connect your WhatsApp Business Account to the Notifyer System to enable automated messaging capabilities

# WhatsApp Business Account Integration

<Frame>
  <iframe title="WhatsApp Business Integration" />
</Frame>

## Overview

Notifyer System enables businesses to send automated WhatsApp messages to customers through a direct integration with the WhatsApp Business Platform. This guide walks you through the embedding process to connect your WhatsApp Business Account with Notifyer System.

<Note>
  This process uses Meta's Embedded Signup flow, which allows you to create or connect your WhatsApp Business Account directly within Notifyer System.
</Note>

## Prerequisites

<Check>
  Active Notifyer System account with a subscription plan or pay-as-you-go credit
</Check>

<Check>
  Meta Business Portfolio (or willingness to create one during the process)
</Check>

<Check>
  A business phone number you control. If that number already uses the **WhatsApp Business app**, keep the app — Notifyer supports Meta WhatsApp Coexistence
</Check>

<Warning>
  Coexistence applies to the **WhatsApp Business app**. You do **not** delete that app to work with Notifyer. If the number is on the consumer WhatsApp app instead, migrate it to WhatsApp Business or use a different number.
</Warning>

## Integration Process

<Steps>
  <Step title="Access the Connection Flow">
    <Accordion title="Navigating to the Connection Page">
      1. Log in to your Notifyer System dashboard
      2. Navigate to **Your Templates** section
      3. Make sure you're on the **Connect to WhatsApp** tab
      4. Click the **Connect your WhatsApp Number** button in the center of the page

      <Frame>
        <img />
      </Frame>
    </Accordion>

    <Tip>
      You can track your progress through the onboarding process using the steps indicator in the bottom-left corner of the screen.
    </Tip>
  </Step>

  <Step title="Connect with Facebook">
    1. Log in with your Facebook account when prompted
    2. If already logged in, click **Continue as \[your Facebook username]**
    3. Review the permissions Notifyer System is requesting
    4. Click **Get Started** to begin the configuration process

    <Frame>
      <img alt="Connecting with Facebook" />
    </Frame>
  </Step>

  <Step title="Complete the 6-Step Configuration">
    <Accordion title="Step 1: Business Information" icon="building">
      <ResponseField name="Business Portfolio" type="dropdown">
        Select an existing business portfolio or create a new one
      </ResponseField>

      <Accordion title="Create a business portfolio" icon="circle-check">
        If you choose to create a new business portfolio, fill out the required fields:

        <ResponseField name="Business Name" type="string">
          Your official business name (must be unique among your portfolios)
        </ResponseField>

        <ResponseField name="Business Email Address" type="string">
          A valid email that can receive verification messages
        </ResponseField>

        <ResponseField name="Business Website or Profile" type="string">
          Your business website URL or social media profile
        </ResponseField>

        <ResponseField name="Country" type="string">
          Country where your business is located
        </ResponseField>

        <Frame>
          <img alt="Entering required information in Business Information section" />
        </Frame>
      </Accordion>

      <Accordion title="Existing Portfolios" icon="circle-check">
        Choose a business portfolio you've already configured in Meta Business Suite

        <Info>
          See how to [create a business portfolio in Meta Business Suite and Business Manager.](https://www.facebook.com/business/help/1710077379203657)

          If you select an existing portfolio, your business name, website, and country will be automatically populated from your Meta Business configuration.
        </Info>
      </Accordion>
    </Accordion>

    <Accordion title="Step 2: Select WhatsApp Business Account" icon="message">
      <ResponseField name="WhatsApp Business Account" type="radio">
        Select whether to create a new account or use an existing one
      </ResponseField>

      <Expandable title="Account Options">
        <ResponseField name="Create new account" type="option">
          **Recommended** for first-time users (default option)
        </ResponseField>

        <ResponseField name="Select existing account" type="option">
          Only available if you have existing WhatsApp Business accounts
        </ResponseField>
      </Expandable>

      <ResponseField name="WhatsApp Business Profile" type="radio">
        Select whether to create a new profile or use an existing one
      </ResponseField>

      <Expandable title="Profile Options">
        <ResponseField name="Create new profile" type="option">
          **Recommended** for first-time users (default option)
        </ResponseField>

        <ResponseField name="Select existing profile" type="option">
          Only available if you connect an existing WhatsApp Business profile
        </ResponseField>
      </Expandable>

      <br />

      <Frame>
        <img alt="Selecting options for WhatsApp Business Account and Profile" />
      </Frame>
    </Accordion>

    <Accordion title="Step 3: Business Profile Setup" icon="id-card">
      <ResponseField name="WhatsApp Business Account Name" type="string">
        The internal name of your account (used for management purposes)
      </ResponseField>

      <ResponseField name="WhatsApp Business Display Name" type="string">
        The name your customers will see when receiving messages from your business

        <Warning>
          This is the name your customers will see when receiving messages from your business. Choose carefully as it impacts brand recognition.
        </Warning>
      </ResponseField>

      <ResponseField name="Category" type="dropdown">
        Business category that best represents your industry (will be displayed on your profile)
      </ResponseField>

      <Frame>
        <img alt="Entering required information in Create a WhatsApp business profile section" />
      </Frame>
    </Accordion>

    <Accordion title="Step 4: Phone Number Configuration" icon="phone">
      <ResponseField name="Phone Number Method" type="radio">
        Choose how to add your phone number
      </ResponseField>

      <Expandable title="Phone Number Options">
        <ResponseField name="Add a new number (Recommended)" type="option">
          Use your own business phone number
        </ResponseField>

        <ResponseField name="Free WhatsApp number (Not Recommended)" type="option">
          WhatsApp will generate a +1 555 number (limited functionality)
        </ResponseField>
      </Expandable>

      <ResponseField name="Verification Method" type="radio">
        Choose how to receive your verification code
      </ResponseField>

      <Expandable title="Verification Options">
        <ResponseField name="Text message" type="option">
          Receive verification code via SMS
        </ResponseField>

        <ResponseField name="Phone call" type="option">
          Receive verification code via automated call
        </ResponseField>
      </Expandable>

      <br />

      <Frame>
        <img alt="Entering required informstion in Create a WhatsApp business profile section" />
      </Frame>
    </Accordion>

    <Accordion title="Step 5: Number Verification" icon="shield-check">
      Enter the verification code received via your selected method

      <Frame>
        <img alt="Entering required informstion in Create a WhatsApp business profile section" />
      </Frame>
    </Accordion>

    <Accordion title="Step 6: Payment Method Setup" icon="credit-card">
      1. After verification, you'll see a "You're now ready to chat with people on WhatsApp" screen
      2. Click the **Add Payment Method** button
      3. You'll be redirected to the Facebook Business "Billing & Payments" page
      4. Select "Payment Methods" from the left menu
      5. Ensure you're on the "WhatsApp Business accounts" tab
      6. Select your WhatsApp account from the dropdown (verify WhatsApp account ID)
      7. Click "Add Payment Method" and provide the required information
      8. Set your payment method as the default option
    </Accordion>
  </Step>

  <Step title="Complete Business Verification">
    <Warning>
      This step is critical for ensuring you can send messages without restrictions. Unverified businesses may experience limited functionality.
    </Warning>

    1. Navigate to Settings in your Facebook Business Manager
    2. Select "WhatsApp accounts" under the "Accounts" section
    3. Scroll down to the "Business verification" section
    4. Click "Start verification" to access the Security Center
    5. Complete the business verification process by providing the requested business information and documentation
  </Step>
</Steps>

## Account Dashboard Overview

Once your WhatsApp Business Account is connected, you'll have access to the following tabs in the "Your Templates" section:

<CardGroup>
  <Card title="Sign Up" icon="user-plus">
    Connect your WhatsApp Business Account using the "Sign up with Facebook" option
  </Card>

  <Card title="Create Template" icon="pen-to-square">
    Design message templates and submit them to Meta for approval
  </Card>

  <Card title="Templates" icon="clipboard-list">
    View, manage, and monitor the approval status of your message templates
  </Card>
</CardGroup>

## Integration Options

After successfully embedding your WhatsApp Business Account, you can integrate Notifyer System with your preferred automation platform:

<AccordionGroup>
  <Accordion title="Make Integration" icon="lines-leaning">
    Connect Notifyer System with Make to create powerful automation workflows.

    [View Make Documentation →](https://docs.whatsable.app/guides/notifier-system/make-overview)
  </Accordion>

  <Accordion title="Zapier Integration" icon="bolt">
    Integrate with Zapier to connect WhatsApp messaging with thousands of applications.

    [View Zapier Documentation →](https://docs.whatsable.app/guides/notifier-system/zapier-overview)
  </Accordion>

  <Accordion title="n8n Integration" icon="diagram-project">
    Use n8n for advanced workflow automation with WhatsApp messaging.

    [View n8n Documentation →](https://docs.whatsable.app/guides/notifier-system/n8n-overview)
  </Accordion>

  <Accordion title="Direct API Integration" icon="code">
    Implement custom integrations using our comprehensive API.

    [Try API Reference →](https://docs.whatsable.app/api-reference/introduction)
  </Accordion>
</AccordionGroup>

## API Reference

<CardGroup>
  <Card title="Get Templates" icon="list" href="https://docs.whatsable.app/guides/notifier-system/api/get-templates">
    Retrieve all your approved message templates
  </Card>

  <Card title="Send Template Message" icon="paper-plane" href="https://docs.whatsable.app/guides/notifier-system/api/template-message">
    Send messages using your approved templates
  </Card>

  <Card title="Incoming Message" icon="inbox" href="https://docs.whatsable.app/guides/notifier-system/api/incoming-message">
    Handle incoming messages from customers
  </Card>
</CardGroup>

<Card title="Try it in the API Reference" icon="arrow-right" href="https://docs.whatsable.app/api-reference/">
  Experiment with the Get Templates API and view responses in real-time
</Card>

## Alternative Option: Notifier

<Info>
  If the embedding process is too complex for your needs, you can use Notifier by Whatsable instead, which allows you to send automated messages through our WhatsApp bot without going through the full embedding process.
</Info>

<Card title="Learn More About Notifier" icon="lightbulb" href="https://docs.whatsable.app/guides/notifier/zapier">
  Discover a simpler way to send automated WhatsApp messages using Notifier by Whatsable
</Card>

## Troubleshooting

<Accordion title="Verification Failed" icon="triangle-exclamation">
  If your phone number verification fails:

  1. You do **not** need to delete the WhatsApp Business app. Coexistence is supported — keep using that app on your phone
  2. Wait 24 hours before trying again with the same number
  3. Try a different verification method (SMS vs. call)
  4. Contact support if issues persist
</Accordion>

<Accordion title="Business Verification Issues" icon="building-shield">
  If you encounter problems with business verification:

  1. Ensure all business information is accurate and matches official documents
  2. Provide clear, high-quality images of requested documentation
  3. Allow 1-2 business days for verification review
  4. Submit an appeal if verification is rejected
</Accordion>

## Resources

<CardGroup>
  <Card title="Meta Business Suite" icon="facebook" href="https://business.facebook.com">
    Manage your Meta business profiles and portfolios
  </Card>

  <Card title="WhatsApp Business Platform" icon="whatsapp" href="https://business.whatsapp.com/products/business-platform">
    Learn more about the WhatsApp Business Platform
  </Card>

  <Card title="Embedded Signup Guide" icon="link" href="https://developers.facebook.com/docs/whatsapp/embedded-signup">
    Meta's official documentation on embedded signup
  </Card>
</CardGroup>

## Need help?

Our support team is ready to assist you:

<CardGroup>
  <Card title="Email support" icon="envelope" href="mailto:team@whatsable.app">
    Contact [team@whatsable.app](mailto:team@whatsable.app)
  </Card>

  <Card title="Schedule a demo" icon="calendar" href="https://tidycal.com/axelmeta/whatsapp-notifications-by-whatsable">
    Book a personalized walkthrough
  </Card>

  <Card title="Live chat" icon="message-dots" href="https://console.notifyer-systems.com/">
    Click the chat button in the bottom right corner of the Notifyer System dashboard
  </Card>
</CardGroup>


# Notifier System Features
Source: https://docs.whatsable.app/guides/notifier-system/features

Explore the enterprise features of Notifier System

# Notifier System Features

Notifier System provides comprehensive enterprise-grade features for WhatsApp messaging.

## Core Features

### Message Types

* Text messages
* Media messages (images, documents, audio, video)
* Location sharing
* Contact sharing
* Interactive messages
* List messages
* Button messages
* Product messages
* Order messages

### Message Management

* Message status tracking
* Delivery receipts
* Read receipts
* Message history
* Message templates
* Bulk messaging
* Scheduled messages
* Priority queuing
* Message routing

### Security

* End-to-end encryption
* API key authentication
* Rate limiting
* IP whitelisting
* Two-factor authentication
* Audit logs
* Data encryption at rest
* Compliance monitoring

## Enterprise Features

### Multi-tenant Support

* Multiple business units
* Separate message queues
* Custom branding
* Independent analytics
* Role-based access

### Advanced Templates

* Pre-approved message templates
* Dynamic variables
* Multi-language support
* Template analytics
* Template versioning
* Template approval workflow
* Template categories

### Automation

* Workflow automation
* Conditional messaging
* Event-based triggers
* Custom webhooks
* Integration with third-party services
* Business rules engine
* Custom scripting

### Analytics

* Message delivery rates
* Response times
* User engagement
* Template performance
* Custom reports
* Real-time dashboards
* Export capabilities
* API access

## Best Practices

### Enterprise Setup

* Define clear workflows
* Set up proper monitoring
* Implement security measures
* Configure backup systems
* Document processes

### Message Strategy

* Use approved templates
* Implement proper error handling
* Monitor message status
* Follow WhatsApp guidelines
* Regular template updates
* A/B testing
* Performance optimization

## Next Steps

* Learn about [Integrations](/guides/notifier-system/integrations)
* Explore [Enterprise Features](/guides/notifier-system/enterprise/security)
* Check out our [API Reference](/api-reference/notifier-system)
* Read our [Getting Started](/guides/notifier-system/getting-started) guide


# Getting Started with Notifier System
Source: https://docs.whatsable.app/guides/notifier-system/getting-started

Learn how to get started with Notifier System, the flagship WhatsApp messaging solution

# Getting Started with Notifier System

Notifier System is our flagship WhatsApp messaging solution, designed for enterprise-level communication needs.

## Prerequisites

* WhatsApp Business API account
* Business verification
* Technical team for integration
* Understanding of enterprise messaging
* Your Notifier System API credentials

## Quick Setup

1. Contact our sales team for enterprise setup
2. Complete business verification
3. Set up your WhatsApp Business API account
4. Configure your Notifier System instance
5. Get your API credentials
6. Set up webhooks and monitoring

## First Message

Here's a quick example of sending your first message:

```bash theme={null}
curl -X POST https://api.notifiersystem.com/v1/messages \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+1234567890",
    "template": "enterprise_welcome",
    "variables": {
      "name": "John",
      "company": "Enterprise Corp",
      "department": "Sales"
    },
    "metadata": {
      "campaign_id": "welcome_2024",
      "segment": "enterprise",
      "priority": "high"
    }
  }'
```

## Enterprise Features

* Multi-tenant support
* Role-based access control
* Advanced security features
* Custom integrations
* Enterprise-grade support

## Next Steps

* Learn about [Features](/guides/notifier-system/features)
* Explore [Integrations](/guides/notifier-system/integrations)
* Check out [Enterprise Features](/guides/notifier-system/enterprise/security)
* Review our [API Reference](/api-reference/notifier-system)


# Notifier System Integrations
Source: https://docs.whatsable.app/guides/notifier-system/integrations

Learn how to integrate Notifier System with your enterprise applications

# Notifier System Integrations

Integrate Notifier System with your enterprise tools and platforms.

## Available Integrations

### Enterprise Platforms

* Salesforce
* SAP
* Oracle
* Microsoft Dynamics
* ServiceNow

### CRM Systems

* Salesforce
* HubSpot
* Zoho CRM
* Pipedrive
* Microsoft Dynamics
* Custom CRM solutions

### E-commerce Platforms

* Shopify Plus
* Magento Enterprise
* SAP Commerce
* Oracle Commerce
* Custom e-commerce solutions

### Marketing Tools

* Adobe Marketing Cloud
* Salesforce Marketing Cloud
* Oracle Marketing Cloud
* HubSpot Enterprise
* Custom marketing platforms

## Custom Integration

### REST API

```javascript theme={null}
const axios = require('axios');

const sendEnterpriseMessage = async (message) => {
  try {
    const response = await axios.post(
      'https://api.notifiersystem.com/v1/messages',
      message,
      {
        headers: {
          'Authorization': `Bearer ${process.env.NOTIFIER_SYSTEM_API_KEY}`,
          'Content-Type': 'application/json',
          'X-Tenant-ID': process.env.TENANT_ID
        }
      }
    );
    return response.data;
  } catch (error) {
    console.error('Error sending message:', error);
    throw error;
  }
};
```

### Webhooks

Configure webhooks for enterprise-level monitoring:

```json theme={null}
{
  "event": "message.status",
  "data": {
    "message_id": "msg_123",
    "status": "delivered",
    "template": "enterprise_welcome",
    "variables": {
      "name": "John",
      "company": "Enterprise Corp",
      "department": "Sales"
    },
    "metadata": {
      "campaign_id": "welcome_2024",
      "segment": "enterprise",
      "priority": "high"
    },
    "timestamp": "2024-03-20T10:00:00Z"
  }
}
```

## Enterprise Features

### Multi-tenant Support

* Separate API keys per tenant
* Custom webhook endpoints
* Tenant-specific templates
* Independent analytics
* Custom branding

### Security

* IP whitelisting
* API key rotation
* Audit logging
* Data encryption
* Compliance monitoring

### Monitoring

* Real-time status
* Error tracking
* Performance metrics
* Usage analytics
* Cost tracking

## Best Practices

### Integration

* Use environment variables
* Implement retry logic
* Handle rate limits
* Monitor webhook delivery
* Use template variables
* Implement proper error handling
* Set up monitoring
* Regular security audits

### Development

* Follow API guidelines
* Use SDK when available
* Test thoroughly
* Document integration
* Version control
* CI/CD pipeline
* Regular updates

## Next Steps

* Read our [Getting Started](/guides/notifier-system/getting-started) guide
* Explore [Features](/guides/notifier-system/features)
* Check out [Enterprise Features](/guides/notifier-system/enterprise/security)
* Review our [API Reference](/api-reference/notifier-system)


# Make
Source: https://docs.whatsable.app/guides/notifier-system/make-overview

Learn how to seamlessly integrate Make with the Notifyer System for enterprise-level WhatsApp automation

# Notifyer System Integration with Make

<Frame>
  <img />
</Frame>

<Tip>
  This guide walks you through connecting Notifyer System with Make to create powerful automated WhatsApp messaging workflows for your business
</Tip>

## Prerequisites

Before getting started, make sure you have:

<CardGroup>
  <Card title="Notifyer System Account" icon="user">
    Active Notifyer System account with a subscription plan (Monthly or Pay-as-you-go)
  </Card>

  <Card title="Make Account" icon="user">
    Access to [Make](https://www.make.com/en/register) workflow automation platform
  </Card>
</CardGroup>

<Tip>
  New to Notifyer System? [Sign up here](https://console.notifyer-systems.com/)
</Tip>

## Setting up your Notifyer System account

<Steps>
  <Step title="Complete the Embedding Process">
    Before sending WhatsApp messages, you must complete the platform embedding process, which connects your WhatsApp Business account to Notifyer System.

    <Info>
      The embedding process is required by Meta to ensure proper business verification and compliance with WhatsApp Business Platform policies.
    </Info>
  </Step>

  <Step title="Set up message templates">
    Notifyer System provides two methods for sending WhatsApp messages:

    <Accordion title="Option A: Template messages">
      <p>WhatsApp templates are pre-approved message formats that allow for personalization while maintaining compliance with WhatsApp policies.</p>

      <Steps>
        <Step title="Navigate to Templates">
          Go to **Your Templates** in your Notifyer dashboard
        </Step>

        <Step title="Create Template">
          Click the **Create Template** tab at the top of the page
        </Step>

        <Step title="Fill out the form">
          Complete the template creation form with the following details:

          <ResponseField name="Template Name" type="string">
            Choose a descriptive name for internal reference
          </ResponseField>

          <ResponseField name="Language" type="string">
            Choose your template's primary language
          </ResponseField>

          <ResponseField name="Category" type="string">
            Select the appropriate message category
          </ResponseField>

          <ResponseField name="Header" type="image | document | video">
            Optional: Add an image, document, or video header
          </ResponseField>

          <ResponseField name="Message Body" type="string">
            Craft your message content
          </ResponseField>

          <ResponseField name="Variables" type="string">
            Add placeholders using `{{1}}`, `{{2}}` format for personalization
          </ResponseField>

          <ResponseField name="Buttons" type="button">
            Optional: Configure call-to-action buttons
          </ResponseField>
        </Step>

        <Step title="Submit for review">
          Click **Preview and Submit**
        </Step>
      </Steps>

      <Frame>
        <img alt="Template Creation Interface" />
      </Frame>

      <Warning>
        Templates typically get reviewed within 24 hours. Creating compliant templates that avoid promotional language increases approval chances.
      </Warning>
    </Accordion>

    <Accordion title="Option B: Non-template messages">
      <p>For simpler communications, you can send non-template messages that include:</p>

      <CardGroup>
        <Card title="Text" icon="message-text">
          Plain text messages within the 24-hour window
        </Card>

        <Card title="Images" icon="image">
          Photos and graphics in supported formats
        </Card>

        <Card title="Documents" icon="file-pdf">
          PDFs, Word docs, and other file types
        </Card>

        <Card title="Videos" icon="video">
          MP4 and other supported video formats
        </Card>
      </CardGroup>

      <Note>
        Non-template messages can only be sent within the 24-hour customer service window after a customer initiates contact with your business.
      </Note>
    </Accordion>
  </Step>

  <Step title="Get your API key">
    To connect Notifyer System with Make, you'll need an API key:

    1. In your Notifyer dashboard, navigate to [**API Keys**](https://console.notifyer-systems.com/api-key)
    2. Copy your unique API key
    3. Store it securely—you'll need it for the integration

    <Warning>
      Never share your API key publicly or commit it to version control systems.
    </Warning>

    <Frame>
      <img alt="API Key Location" />
    </Frame>
  </Step>
</Steps>

## Connect Notifyer System to Make

Now that you have Notifyer System set up, let's connect it to Make to automate your scenarios.

<Steps>
  <Step title="Install Notifyer System in Make">
    1. Log in to your Make account
    2. Navigate to Notifyer System dashboard and select **Connect to Make** in the side menu
    3. Click **Continue** in the connection guide popup
    4. Click **Install**, select your organization at the bottom of the screen, then click **Install** again. (Note: You need Admin, Owner, or App Developer role in your organization to install apps.)

    <Check>
      You're now ready to create scenarios with the Notifyer System app
    </Check>

    <Frame>
      <img alt="Installing Notifyer System in Make" />
    </Frame>
  </Step>

  <Step title="Set up your Make Scenario">
    1. Log in to your Make account
    2. Create a new scenario by clicking **+ Create a new scenario**
    3. (Optional) Add a trigger module of your choice:
       * Popular triggers include Google Forms, Jotform, ClickUp, or a Schedule trigger
       * Connect and configure your trigger according to your use case

    <Frame>
      <img alt="Setting up a module/trigger Make" />
    </Frame>
  </Step>

  <Step title="Add the Notifyer System module">
    1. Click the **+** button to add a new module
    2. Search for **Notifyer System** in the apps or modules library
    3. Select the module with the official Notifyer System logo

    <Frame>
      <img alt="Adding the Notifyer System module" />
    </Frame>
  </Step>

  <Step title="Configure Notifyer System credentials">
    <Accordion title="Credential Setup">
      1. Once you click on Notifyer System module, select '**Send a WhatsApp Message with Your Template**' or '**Send a WhatsApp Message without Template**' from the **ACTIONS**
      2. Click **Create a connection** in the **Connection** section of Notifyer System module and you will be prompted to enter your API Key
      3. Enter your Notifyer System API key that you copied earlier
      4. Rename your connection name if needed
      5. Click **Save** to store your credential

      <Frame>
        <img alt="Configuring Notifyer System credentials" />
      </Frame>
    </Accordion>
  </Step>

  <Step title="Configure your message">
    Depending on your messaging needs, choose one of the following operations:

    <Tabs>
      <Tab title="Send a WhatsApp Message with Your Template">
        Complete the required fields:

        <ResponseField name="Phone Number" type="string">
          Enter the recipient's phone number with country code (e.g., +1234567890) or use dynamic data from previous nodes
        </ResponseField>

        <ResponseField name="Templates" type="dropdown">
          Select from your pre-approved templates in the dropdown
        </ResponseField>

        <ResponseField name="Media" type="string">
          Enter publicly accessible media URL for Media (image/video/document) header.

          <Info>
            This field will only appear if you have a Media (image/video/document) header configured in your selected template.
          </Info>
        </ResponseField>

        <ResponseField name="Variables" type="string">
          Fill in values for each variable in your template, mapping them to dynamic data when applicable
        </ResponseField>

        <ResponseField name="Add a Note" type="string">
          Add note for internal tracking. This data won't be sent to the recipient
        </ResponseField>

        <ResponseField name="Add Label(s)" type="multiselect">
          Select label(s) for internal tracking. This data won't be sent to the recipient
        </ResponseField>

        <Frame>
          <img alt="Template Message Configuration" />
        </Frame>
      </Tab>

      <Tab title="Send a WhatsApp Message without Template">
        Complete the required fields:

        <ResponseField name="Phone Number" type="string">
          Enter the recipient's phone number with country code (e.g., +1234567890) or use dynamic data from previous nodes
        </ResponseField>

        <ResponseField name="Message Type" type="dropdown">
          Choose from the following message types:

          <CardGroup>
            <Card title="Text Message" icon="message">
              For plain text messages
            </Card>

            <Card title="Media Message (Image)" icon="image">
              For sending images (JPEG, PNG, etc.)
            </Card>

            <Card title="Media Message (Video)" icon="video">
              For sending videos (MP4, 3GP, etc.)
            </Card>

            <Card title="Document Message" icon="file">
              For sending documents (PDF, Word, etc.)
            </Card>

            <Card title="Audio Message" icon="volume">
              For sending videos (MP3, OGG, etc.)
            </Card>

            <Card title="Interactive URL Button" icon="square-arrow-up-right">
              For messages with button that contain URL or dynamic URL
            </Card>
          </CardGroup>
        </ResponseField>

        <ResponseField name="Message Details" type="object">
          <Tabs>
            <Tab title="Text Message">
              <Steps>
                <Step title="Message Details">
                  <ResponseField name="Enable Link Preview" type="option">
                    Keep the option at the default 'No'. If there is a link/URL in the text body and you want the recipient to see a preview, select 'Yes'
                  </ResponseField>

                  <ResponseField name="Message Text" type="string">
                    Enter the text message content
                  </ResponseField>
                </Step>
              </Steps>
            </Tab>

            <Tab title="Media Message (Image)">
              <Steps>
                <Step title="Image Details">
                  <ResponseField name="Image URL" type="url">
                    Enter the publicly accessible URL for your image file
                  </ResponseField>

                  <ResponseField name="Caption" type="string">
                    Optional caption for the image
                  </ResponseField>
                </Step>
              </Steps>
            </Tab>

            <Tab title="Media Message (Video)">
              <Steps>
                <Step title="Video Details">
                  <ResponseField name="Video URL" type="url">
                    Enter the publicly accessible URL for your video file
                  </ResponseField>

                  <ResponseField name="Caption" type="string">
                    Optional caption for the video
                  </ResponseField>
                </Step>
              </Steps>
            </Tab>

            <Tab title="Document Message">
              <Steps>
                <Step title="Document Details">
                  <ResponseField name="Document URL" type="url">
                    Enter the publicly accessible URL for your document
                  </ResponseField>

                  <ResponseField name="Caption" type="string">
                    Optional caption for the document
                  </ResponseField>
                </Step>

                <Step>
                  <ResponseField name="Filename" type="string">
                    Enter the filename (e.g., report.pdf)
                  </ResponseField>
                </Step>
              </Steps>
            </Tab>

            <Tab title="Audio Message">
              <Step title="Document Details">
                <ResponseField name="Audio URL" type="url">
                  Enter the publicly accessible URL for your audio file (MP3, OGG)
                </ResponseField>
              </Step>
            </Tab>

            <Tab title="Interactive URL Button">
              <Steps>
                <Step title="Interactive Message Details">
                  <ResponseField name="Header Text" type="string">
                    Enter optional text to show at the top
                  </ResponseField>

                  <ResponseField name="Message Body" type="string">
                    Enter the main content of the message
                  </ResponseField>

                  <ResponseField name="Button Text" type="string">
                    Enter the text to display on button
                  </ResponseField>

                  <ResponseField name="Button URL" type="url">
                    Enter the URL for the button
                  </ResponseField>

                  <ResponseField name="Footer Text" type="string">
                    Enter the optional text to show at bottom
                  </ResponseField>
                </Step>
              </Steps>
            </Tab>
          </Tabs>
        </ResponseField>

        <ResponseField name="Add Label(s)" type="multiselect">
          Select label(s) for internal tracking. This data won't be sent to the recipient
        </ResponseField>

        <Frame>
          <img alt="Non-Template Message Configuration" />
        </Frame>
      </Tab>
    </Tabs>
  </Step>

  <Step title="Test and activate your scenario">
    1. Click **Save** to save your message configuration
    2. Right click on the Whatsable module and select **Run this module only** to verify the module is working correctly
       * or click **Run once** in the bottom-left corner of the screen to test the entire scenario
    3. If the test is successful, you'll see a confirmation message
    4. Click **Save** icon in the bottom-left corner to save your scenario (You can also set timer intarval for the scenario)
    5. Toggle the **Active** switch in the bottom-left corner with time to activate your scenario

    <Frame>
      <img alt="Testing and activating your scenario" />
    </Frame>
  </Step>
</Steps>

## Example use cases

<CardGroup>
  <Card title="Order confirmations" icon="box-check">
    Send automatic order confirmations when new orders are placed
  </Card>

  <Card title="Appointment reminders" icon="calendar">
    Schedule reminders before upcoming appointments
  </Card>

  <Card title="Lead notifications" icon="user-plus">
    Alert your sales team when new leads come in
  </Card>

  <Card title="Customer support" icon="headset">
    Route support inquiries to the appropriate team member
  </Card>

  <Card title="Delivery updates" icon="truck">
    Keep customers informed about their delivery status
  </Card>

  <Card title="Payment reminders" icon="credit-card">
    Send automatic payment reminders for overdue accounts
  </Card>
</CardGroup>

## Best practices

<AccordionGroup>
  <Accordion title="Test thoroughly" icon="vial">
    Always test your workflows with test phone numbers before activating them for production use.
  </Accordion>

  <Accordion title="Use templates" icon="file-lines">
    Whenever possible, use pre-approved templates for better deliverability and compliance.
  </Accordion>

  <Accordion title="Add personalization" icon="user">
    Include customer names and specific details to increase engagement and response rates.
  </Accordion>

  <Accordion title="Follow WhatsApp policies" icon="shield-check">
    Ensure all message content complies with WhatsApp Business policies to avoid account restrictions.
  </Accordion>

  <Accordion title="Monitor performance" icon="chart-line">
    Regularly check your message delivery rates in your Notifyer dashboard.
  </Accordion>
</AccordionGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Messages not sending?" icon="circle-exclamation">
    <Steps>
      <Step title="Verify API key">
        Ensure your API key is entered correctly in the Make credentials
      </Step>

      <Step title="Check phone numbers">
        Confirm phone numbers are in the correct international format (e.g., +14155552671)
      </Step>

      <Step title="Check subscription">
        Verify your Notifyer subscription is active and has available credits
      </Step>

      <Step title="Template verification">
        For template messages, ensure you're using an approved template
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Template errors?" icon="file-exclamation">
    <Steps>
      <Step title="Variable check">
        Verify all required variables are included in your template message
      </Step>

      <Step title="Format verification">
        Check that variable formats match the expected values (text, number, date, etc.)
      </Step>

      <Step title="Template name">
        Ensure you're using the correct template name exactly as it appears in your dashboard
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Media not displaying?" icon="image">
    <Steps>
      <Step title="URL access">
        Confirm your media URLs are publicly accessible (test in an incognito browser)
      </Step>

      <Step title="File format">
        Verify the file format is supported by WhatsApp
      </Step>

      <Step title="File size">
        Check that file sizes are within WhatsApp limits:

        * Images: up to 5MB
        * Videos: up to 16MB
        * Documents: up to 100MB
      </Step>
    </Steps>
  </Accordion>
</AccordionGroup>

## Need help?

Our support team is ready to assist you:

<CardGroup>
  <Card title="Email support" icon="envelope" href="mailto:team@whatsable.app">
    Contact [team@whatsable.app](mailto:team@whatsable.app)
  </Card>

  <Card title="Schedule a demo" icon="calendar" href="https://tidycal.com/axelmeta/notifyer-systems-demo">
    Book a personalized walkthrough
  </Card>

  <Card title="Live chat" icon="message-dots" href="">
    Click the green chat button in the bottom right corner of the Notifyer System dashboard
  </Card>
</CardGroup>

<Info>
  For additional automation platform integrations (Make.com, Zapier, etc.), please contact our support team or check our integration documentation.
</Info>


# n8n
Source: https://docs.whatsable.app/guides/notifier-system/n8n-overview

Learn how to seamlessly integrate n8n with the Notifyer System for enterprise-level WhatsApp automation

# Notifyer System Integration with n8n

<Frame>
  <img />
</Frame>

<Tip>
  This guide walks you through connecting Notifyer System with n8n to create powerful automated WhatsApp messaging workflows for your business
</Tip>

## Prerequisites

Before getting started, make sure you have:

<CardGroup>
  <Card title="Notifyer System Account" icon="user">
    Active Notifyer System account with a subscription plan (Monthly or Pay-as-you-go)
  </Card>

  <Card title="n8n Account" icon="user">
    Access to [n8n](https://app.n8n.cloud/login) workflow automation platform
  </Card>
</CardGroup>

<Tip>
  New to Notifyer System? [Sign up here](https://console.notifyer-systems.com/)
</Tip>

## Setting up your Notifyer System account

<Steps>
  <Step title="Complete the Embedding Process">
    Before sending WhatsApp messages, you must complete the platform embedding process, which connects your WhatsApp Business account to Notifyer System.

    <Info>
      The embedding process is required by Meta to ensure proper business verification and compliance with WhatsApp Business Platform policies.
    </Info>
  </Step>

  <Step title="Set up message templates">
    Notifyer System provides two methods for sending WhatsApp messages:

    <Accordion title="Option A: Template messages">
      <p>WhatsApp templates are pre-approved message formats that allow for personalization while maintaining compliance with WhatsApp policies.</p>

      <Steps>
        <Step title="Navigate to Templates">
          Go to **Your Templates** in your Notifyer dashboard
        </Step>

        <Step title="Create Template">
          Click the **Create Template** tab at the top of the page
        </Step>

        <Step title="Fill out the form">
          Complete the template creation form with the following details:

          <ResponseField name="Template Name" type="string">
            Choose a descriptive name for internal reference
          </ResponseField>

          <ResponseField name="Language" type="string">
            Choose your template's primary language
          </ResponseField>

          <ResponseField name="Category" type="string">
            Select the appropriate message category
          </ResponseField>

          <ResponseField name="Header" type="image | document | video">
            Optional: Add an image, document, or video header
          </ResponseField>

          <ResponseField name="Message Body" type="string">
            Craft your message content
          </ResponseField>

          <ResponseField name="Variables" type="string">
            Add placeholders using `{{1}}`, `{{2}}` format for personalization
          </ResponseField>

          <ResponseField name="Buttons" type="button">
            Optional: Configure call-to-action buttons
          </ResponseField>
        </Step>

        <Step title="Submit for review">
          Click **Preview and Submit**
        </Step>
      </Steps>

      <Frame>
        <img alt="Template Creation Interface" />
      </Frame>

      <Warning>
        Templates typically get reviewed within 24 hours. Creating compliant templates that avoid promotional language increases approval chances.
      </Warning>
    </Accordion>

    <Accordion title="Option B: Non-template messages">
      <p>For simpler communications, you can send non-template messages that include:</p>

      <CardGroup>
        <Card title="Text" icon="message-text">
          Plain text messages within the 24-hour window
        </Card>

        <Card title="Images" icon="image">
          Photos and graphics in supported formats
        </Card>

        <Card title="Documents" icon="file-pdf">
          PDFs, Word docs, and other file types
        </Card>

        <Card title="Videos" icon="video">
          MP4 and other supported video formats
        </Card>
      </CardGroup>

      <Note>
        Non-template messages can only be sent within the 24-hour customer service window after a customer initiates contact with your business.
      </Note>
    </Accordion>
  </Step>

  <Step title="Get your API key">
    To connect Notifyer System with n8n, you'll need an API key:

    1. In your Notifyer dashboard, navigate to [**API Keys**](https://console.notifyer-systems.com/api-key)
    2. Copy your unique API key
    3. Store it securely—you'll need it for the integration

    <Warning>
      Never share your API key publicly or commit it to version control systems.
    </Warning>

    <Frame>
      <img alt="API Key Location" />
    </Frame>
  </Step>
</Steps>

## Integrating with n8n

<Steps>
  <Step title="Set up your n8n workflow">
    1. Log in to your n8n account
    2. Create a new workflow by clicking **Create Workflow**
    3. Add a trigger node of your choice:
       * Popular triggers include Google Forms, Jotform, ClickUp, or a Schedule trigger
       * Connect and configure your trigger according to your use case

    <Accordion title="Whatsable trigger node (optional)">
      <Info>
        The Whatsable trigger node enables your workflow to respond automatically to incoming WhatsApp messages. This setup is optional but recommended for building reactive communication flows.
      </Info>

      <Steps>
        <Step title="Add Whatsable trigger node">
          Follow these steps to add the Whatsable trigger node to your workflow:

          1. Click the **+** button in your workflow canvas to add a new node
          2. Search for "Whatsable" in the node library search bar
          3. Select the node displaying the official Whatsable logo
          4. From the available trigger options, choose **On new Incoming message event**

          <Frame>
            <img alt="Whatsable node selection showing trigger options" />
          </Frame>

          <Tip>
            The trigger node will automatically listen for incoming messages and initiate your workflow when a new message is received.
          </Tip>
        </Step>

        <Step title="Configure authentication credentials">
          Set up your Whatsable API credentials to establish a secure connection:

          **Webhook URL Configuration:**

          1. In the Whatsable Trigger node parameters, locate the **Webhook URLs** section at the top
          2. Select **Production URL** and copy the generated URL by clicking on it
          3. Store this URL securely as you'll need it for the credential setup

          <Frame>
            <img alt="Production URL selection and copy interface" />
          </Frame>

          **Credential Creation:**

          1. In the **Credential to connect with** dropdown, click **+ Create new credential**
          2. Select **Whatsable Notifyer System API** as your connection method
          3. Enter your Notifyer System API key in the **API Key** field
          4. Paste the Production URL you copied earlier into the **Production URL** field
          5. Assign a descriptive name to your credential (e.g., "Whatsable Production")
          6. Click **Save** to securely store your credentials

          <Frame>
            <img alt="Whatsable credential configuration interface" />
          </Frame>

          <Note>
            Your API credentials are encrypted and stored securely. Never share your API key publicly or commit it to version control.
          </Note>
        </Step>

        <Step title="Test and activate workflow">
          Complete the setup by testing and activating your trigger:

          **Response Configuration:**

          1. In the **Respond** dropdown, select your preferred response timing:
             * **Immediately**: Responds as soon as the trigger fires
             * **When Last Node Finishes**: Waits for the entire workflow to complete before responding

          **Testing:**

          1. Click **Execute step** on the Whatsable node to run a test
          2. Verify the connection is working by checking for a success confirmation
          3. Review any error messages if the test fails and adjust your configuration accordingly

          <Check>
            Once activated, your workflow will automatically process incoming messages according to your configured logic.
          </Check>

          <Warning>
            Remember to test your workflow thoroughly before activating it in production to ensure it behaves as expected.
          </Warning>
        </Step>
      </Steps>
    </Accordion>
  </Step>

  <Step title="Add the Notifyer System node">
    1. Click the **+** button after your trigger node
    2. Search for "Whatsable" in the nodes panel
    3. Select the node with the official Whatsable logo
    4. After selecting the Whatsable node, choose 'Send template via Notifyer' or 'Send non-template via Notifyer' as needed.

    <Frame>
      <img alt="Whatsable node selection" />
    </Frame>
  </Step>

  <Step title="Configure Notifyer System credential">
    1. In the Whatsable node **Parameters**, find the **Credential to connect with** dropdown
    2. Select **+ Create new credential**
    3. Enter your Notifyer System API key that you copied earlier
    4. Name your credential (e.g., "Notifyer Production")
    5. Click **Save** to store your credential

    <Frame>
      <img alt="Configuring Notifyer System credential" />
    </Frame>
  </Step>

  <Step title="Configure your message">
    1. In **Resource** dropdown, select **Send Message**
    2. In the **Operation** dropdown, choose **Send template via Notifyer** for template messages or **Send non‑template via Notifyer** for regular messages (only works within the 24‑hour window).
    3. Complete the required fields:

    <Tabs>
      <Tab title="Operation: Send template via Notifyer">
        <Steps>
          <Step title="Configure message">
            Complete the required fields:

            <ResponseField name="Recipient" type="string">
              Enter the recipient's phone number with country code (e.g., +14155552671) or use dynamic data from previous nodes
            </ResponseField>

            <ResponseField name="Template Name or ID" type="dropdown">
              Select from your pre-approved templates in the dropdown
            </ResponseField>

            <ResponseField name="Template message details" type="string">
              Based on your selected Template message type, fill in the required fields:

              * For text messages: Enter your message content
              * For media messages: Provide a publicly accessible URL to your file
              * Optional caption (for media files)

              <Warning>
                For all media types, ensure your file URLs are publicly accessible and match the supported file formats.
              </Warning>
            </ResponseField>

            <ResponseField name="Note" type="string">
              (Optional) Include a note in the template message for internal tracking
            </ResponseField>

            <ResponseField name="Label Names or IDs" type="dropdown">
              (Optional) Select the label(s) you created in Chat Notifyer for internal tracking
            </ResponseField>

            <ResponseField name="Schedule Message" type="selection">
              (Optional) Select the date and time to schedule when your message will be sent
            </ResponseField>
          </Step>
        </Steps>
      </Tab>

      <Tab title="Operation: Send non-template via Notifyer">
        <Steps>
          <Step title="Recipient Phone Number">
            Enter the **Phone Number** with country code
          </Step>

          <Step title="Select message type">
            Choose from the following message types:

            <CardGroup>
              <Card title="Text Message" icon="message">
                For plain text messages
              </Card>

              <Card title="Document Message" icon="file">
                For sending documents (PDF, Word, etc.)
              </Card>

              <Card title="Image Message" icon="image">
                For sending images (JPEG, PNG, etc.)
              </Card>

              <Card title="Video Message" icon="video">
                For sending videos (MP4, 3GP, etc.)
              </Card>
            </CardGroup>
          </Step>

          <Step title="Complete message details">
            Based on your selected message type, fill in the required fields:

            * For text messages: Enter your message content
            * For media messages: Provide a publicly accessible URL to your file
            * Optional caption (for media files)

            <Warning>
              For all media types, ensure your file URLs are publicly accessible and match the supported file formats.
            </Warning>
          </Step>

          <Step title="Label Names or IDs">
            (Optional) Select the label(s) you created in Chat Notifyer for internal tracking
          </Step>

          <Step title="Schedule Message">
            (Optional) Select the date and time to schedule when your message will be sent
          </Step>
        </Steps>
      </Tab>
    </Tabs>
  </Step>

  <Step title="Test and activate your workflow">
    1. Click **Test Step** on the Notifyer node to verify it's working correctly
    2. If the test is successful, you'll see a confirmation message
    3. Return to your workflow
    4. Click **Save** to save your entire workflow
    5. Toggle the **Active** switch in the top-right corner to activate your workflow

    <Check>
      Your automated messaging workflow is now operational! Whenever your trigger conditions are met, n8n will automatically send WhatsApp messages through Notifyer System.
    </Check>
  </Step>
</Steps>

## Example use cases

<CardGroup>
  <Card title="Order confirmations" icon="box-check">
    Send automatic order confirmations when new orders are placed
  </Card>

  <Card title="Appointment reminders" icon="calendar">
    Schedule reminders before upcoming appointments
  </Card>

  <Card title="Lead notifications" icon="user-plus">
    Alert your sales team when new leads come in
  </Card>

  <Card title="Customer support" icon="headset">
    Route support inquiries to the appropriate team member
  </Card>

  <Card title="Delivery updates" icon="truck">
    Keep customers informed about their delivery status
  </Card>

  <Card title="Payment reminders" icon="credit-card">
    Send automatic payment reminders for overdue accounts
  </Card>
</CardGroup>

## Best practices

<AccordionGroup>
  <Accordion title="Test thoroughly" icon="vial">
    Always test your workflows with test phone numbers before activating them for production use.
  </Accordion>

  <Accordion title="Use templates" icon="file-lines">
    Whenever possible, use pre-approved templates for better deliverability and compliance.
  </Accordion>

  <Accordion title="Add personalization" icon="user">
    Include customer names and specific details to increase engagement and response rates.
  </Accordion>

  <Accordion title="Follow WhatsApp policies" icon="shield-check">
    Ensure all message content complies with WhatsApp Business policies to avoid account restrictions.
  </Accordion>

  <Accordion title="Monitor performance" icon="chart-line">
    Regularly check your message delivery rates in your Notifyer dashboard.
  </Accordion>
</AccordionGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Messages not sending?" icon="circle-exclamation">
    <Steps>
      <Step title="Verify API key">
        Ensure your API key is entered correctly in the n8n credentials
      </Step>

      <Step title="Check phone numbers">
        Confirm phone numbers are in the correct international format (e.g., +14155552671)
      </Step>

      <Step title="Check subscription">
        Verify your Notifyer subscription is active and has available credits
      </Step>

      <Step title="Template verification">
        For template messages, ensure you're using an approved template
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Template errors?" icon="file-exclamation">
    <Steps>
      <Step title="Variable check">
        Verify all required variables are included in your template message
      </Step>

      <Step title="Format verification">
        Check that variable formats match the expected values (text, number, date, etc.)
      </Step>

      <Step title="Template name">
        Ensure you're using the correct template name exactly as it appears in your dashboard
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Media not displaying?" icon="image">
    <Steps>
      <Step title="URL access">
        Confirm your media URLs are publicly accessible (test in an incognito browser)
      </Step>

      <Step title="File format">
        Verify the file format is supported by WhatsApp
      </Step>

      <Step title="File size">
        Check that file sizes are within WhatsApp limits:

        * Images: up to 5MB
        * Videos: up to 16MB
        * Documents: up to 100MB
      </Step>
    </Steps>
  </Accordion>
</AccordionGroup>

## Need help?

Our support team is ready to assist you:

<CardGroup>
  <Card title="Email support" icon="envelope" href="mailto:team@whatsable.app">
    Contact [team@whatsable.app](mailto:team@whatsable.app)
  </Card>

  <Card title="Schedule a demo" icon="calendar" href="https://tidycal.com/axelmeta/notifyer-systems-demo">
    Book a personalized walkthrough
  </Card>

  <Card title="Live chat" icon="message-dots" href="">
    Click the green chat button in the bottom right corner of the Notifyer dashboard
  </Card>
</CardGroup>

<Info>
  For additional automation platform integrations (Make.com, Zapier, etc.), please contact our support team or check our integration documentation.
</Info>


# Pipedrive
Source: https://docs.whatsable.app/guides/notifier-system/pipedrive-overview

Learn how to seamlessly integrate Pipedrive with the Notifyer System for automated WhatsApp messaging

# Notifyer System Integration with Pipedrive

<Frame>
  <img />
</Frame>

<Tip>
  This guide walks you through connecting Notifyer System with Pipedrive to create powerful automated WhatsApp messaging workflows for your sales and CRM processes
</Tip>

## Prerequisites

Before getting started, make sure you have:

<CardGroup>
  <Card title="Notifyer System Account" icon="user">
    Active Notifyer System account with a subscription plan (Monthly or Pay-as-you-go)
  </Card>

  <Card title="Pipedrive Account" icon="user">
    Access to [Pipedrive](https://www.pipedrive.com/) CRM platform
  </Card>
</CardGroup>

<Tip>
  New to Notifyer System? [Sign up here](https://console.notifyer-systems.com/)
</Tip>

## Setting up your Notifyer System account

<Steps>
  <Step title="Complete the Embedding Process">
    Before sending WhatsApp messages, you must complete the platform [embedding process](/guides/notifier-system/embedding-process), which connects your WhatsApp Business account to Notifyer System.

    <Info>
      The embedding process is required by Meta to ensure proper business verification and compliance with WhatsApp Business Platform policies.
    </Info>
  </Step>

  <Step title="Set up message templates">
    Notifyer System provides two methods for sending WhatsApp messages:

    <Accordion title="Option A: Template messages">
      <p>WhatsApp templates are pre-approved message formats that allow for personalization while maintaining compliance with WhatsApp policies.</p>

      <Steps>
        <Step title="Navigate to Templates">
          Go to **Your Templates** in your Notifyer dashboard
        </Step>

        <Step title="Create Template">
          Click the **Create Template** tab at the top of the page
        </Step>

        <Step title="Fill out the form">
          Complete the template creation form with the following details:

          <ResponseField name="Template Name" type="string">
            Choose a descriptive name for internal reference
          </ResponseField>

          <ResponseField name="Language" type="string">
            Choose your template's primary language
          </ResponseField>

          <ResponseField name="Category" type="string">
            Select the appropriate message category
          </ResponseField>

          <ResponseField name="Header" type="image | document | video">
            Optional: Add an image, document, or video header
          </ResponseField>

          <ResponseField name="Message Body" type="string">
            Craft your message content
          </ResponseField>

          <ResponseField name="Variables" type="string">
            Add placeholders using `{{1}}`, `{{2}}` format for personalization
          </ResponseField>

          <ResponseField name="Buttons" type="button">
            Optional: Configure call-to-action buttons
          </ResponseField>
        </Step>

        <Step title="Submit for review">
          Click **Preview and Submit**
        </Step>
      </Steps>

      <Frame>
        <img alt="Template Creation Interface" />
      </Frame>

      <Warning>
        Templates typically get reviewed within 24 hours. Creating compliant templates that avoid promotional language increases approval chances.
      </Warning>
    </Accordion>

    <Accordion title="Option B: Non-template messages">
      <p>For simpler communications, you can send non-template messages that include:</p>

      <CardGroup>
        <Card title="Text" icon="message-text">
          Plain text messages within the 24-hour window
        </Card>

        <Card title="Images" icon="image">
          Photos and graphics in supported formats
        </Card>

        <Card title="Documents" icon="file-pdf">
          PDFs, Word docs, and other file types
        </Card>

        <Card title="Videos" icon="video">
          MP4 and other supported video formats
        </Card>
      </CardGroup>

      <Note>
        Non-template messages can only be sent within the 24-hour customer service window after a customer initiates contact with your business.
      </Note>
    </Accordion>
  </Step>

  <Step title="Connect Notifyer System with Pipedrive">
    Follow these simple steps to integrate your Pipedrive account with Notifyer System:

    <Steps>
      <Step title="Access the Integration Page">
        In your Notifyer dashboard, go to [**Connect to Pipedrive**](https://console.notifyer-systems.com/pipedrive).
      </Step>

      <Step title="Initiate the Connection">
        Click the 'Connect Pipedrive Organization' button.
      </Step>

      <Step title="Authorize Access">
        You'll be redirected to Pipedrive's authorization page. Review the permissions and click 'Authorize' to grant Notifyer System access to your Pipedrive organization.
      </Step>

      <Step title="Confirm Connection">
        After authorization, you'll be automatically redirected back to your Notifyer System dashboard. Look for the connection status showing 'Connected to Pipedrive' to confirm the integration was successful.
      </Step>
    </Steps>

    <Frame>
      <img alt="Connecting Notifyer System with Pipedrive" />
    </Frame>
  </Step>
</Steps>

## Sending WhatsApp Messages from Pipedrive

Whatsable's integration with Pipedrive allows you to send WhatsApp messages directly from your deals and contacts without leaving your CRM. This guide will walk you through the complete process.

### Verifying Prerequisites

Before sending WhatsApp messages, ensure the following requirements are met:

<CardGroup>
  <Card title="Whatsable License Status" icon="badge-check">
    Must show as **PAID**
  </Card>

  <Card title="WhatsApp Connection Status" icon="signal">
    Must show as **ACTIVE**
  </Card>

  <Card title="WhatsApp Business Account" icon="whatsapp">
    Must be properly synced with Whatsable
  </Card>
</CardGroup>

<Info>
  You can verify these settings in the Whatsable Integration section of any deal or contact.
</Info>

## Sending Messages from Deals

### Accessing the Whatsable Integration Panel

<Steps>
  <Step title="Navigate to your Pipeline">
    1. Go to your **Pipedrive Dashboard**
    2. Open your desired **Pipeline**
    3. Select a **Deal** from your pipeline
  </Step>

  <Step title="Locate the Integration Panel">
    1. On the right-hand panel, scroll down past the Summary section
    2. Find the **Whatsable Integration** section

    <Frame>
      <img alt="Whatsable Integration Panel" />
    </Frame>
  </Step>
</Steps>

### Understanding the Integration Panel

The Whatsable Integration panel displays important connection information:

<CardGroup>
  <Card title="Whatsable License Status" icon="circle-check">
    Confirms your subscription is active
  </Card>

  <Card title="Synced WhatsApp Account" icon="link">
    Shows which WhatsApp Business account is connected
  </Card>

  <Card title="WhatsApp Connection Status" icon="signal-bars">
    Indicates if your WhatsApp connection is active
  </Card>

  <Card title="Last WhatsApp Communication" icon="clock">
    Displays the date and time of the most recent message
  </Card>

  <Card title="Whatsable Chat URL" icon="arrow-up-right-from-square">
    Provides a direct link to the conversation
  </Card>
</CardGroup>

### Sending Options

Within the Whatsable Integration section, you'll find a green **"Live Chat"** button with a dropdown menu offering three options:

<CardGroup>
  <Card title="Live Chat" icon="messages">
    Opens the Whatsable chat interface directly within Pipedrive
  </Card>

  <Card title="Send Scheduled Message" icon="clock">
    Schedule a message to be sent at a specific date and time
  </Card>

  <Card title="Send Template" icon="paper-plane">
    Send a pre-configured template message immediately
  </Card>
</CardGroup>

## Option 1: Send Scheduled Message

Use this option when you want to send a message at a specific future date and time.

<Steps>
  <Step title="Open the Scheduled Message Modal">
    1. Click the dropdown next to the **Live Chat** button
    2. Select **"Send Scheduled Message"**
    3. A modal window will appear with the following fields
  </Step>

  <Step title="Configure Required Fields">
    <ResponseField name="To" type="string">
      The recipient's phone number(s) associated with the deal. This field is automatically populated from the deal's contact information.
    </ResponseField>

    <ResponseField name="From" type="string">
      Your connected WhatsApp Business account. This field is pre-filled and cannot be modified from this interface.
    </ResponseField>

    <ResponseField name="Select Template" type="dropdown">
      Choose from your pre-created message templates. These templates must be created beforehand in the **Notifyer by Whatsable** dashboard.
    </ResponseField>

    <ResponseField name="Template Variables" type="string">
      Once you select a template, all required placeholder fields will appear dynamically. Fill in each field carefully to personalize your message (e.g., customer name, appointment time, order details).
    </ResponseField>

    <ResponseField name="Scheduled Date and Time" type="datetime">
      Select the exact date and time you want the message to be sent.
    </ResponseField>

    <ResponseField name="Timezone" type="dropdown">
      Specify the timezone from which you're scheduling the message to ensure accurate delivery timing.
    </ResponseField>
  </Step>

  <Step title="Add Optional Information">
    <Expandable title="Optional Fields">
      <ResponseField name="Add a Note" type="text">
        Include an internal note for your team. This note is only visible within Pipedrive and helps with tracking and context.
      </ResponseField>

      <ResponseField name="Select Labels" type="tags">
        Assign labels to categorize and organize your communications for easier filtering and reporting.
      </ResponseField>
    </Expandable>

    <Note>
      At the top of the modal, you'll see your **most recent messages** with this contact (if any previous conversations exist), providing helpful context before sending.
    </Note>
  </Step>

  <Step title="Schedule the Message">
    1. Review all information carefully
    2. Click the **"Schedule Template"** button at the bottom of the modal
    3. Your message is now scheduled and will be sent automatically at the specified time

    <Check>
      Message successfully scheduled! It will be sent at the specified time.
    </Check>

    <Frame>
      <img alt="Schedule Template Modal" />
    </Frame>
  </Step>
</Steps>

## Option 2: Send Template (Immediate)

Use this option to send a pre-configured template message immediately without scheduling.

<Steps>
  <Step title="Open the Send Template Modal">
    1. Click the dropdown next to the **Live Chat** button
    2. Select **"Send Template"**
    3. A modal window will appear with the following fields
  </Step>

  <Step title="Configure Required Fields">
    <ResponseField name="To" type="string">
      The recipient's phone number(s) associated with the deal. This field is automatically populated from the deal's contact information.
    </ResponseField>

    <ResponseField name="From" type="string">
      Your connected WhatsApp Business account. This field is pre-filled and cannot be modified from this interface.
    </ResponseField>

    <ResponseField name="Select Template" type="dropdown">
      Choose from your pre-created message templates. These templates must be created beforehand in the **Notifyer by Whatsable** dashboard.
    </ResponseField>

    <ResponseField name="Template Variables" type="string">
      Once you select a template, all required placeholder fields will appear dynamically. Fill in each field carefully to personalize your message (e.g., customer name, product details, tracking numbers).
    </ResponseField>
  </Step>

  <Step title="Add Optional Information">
    <Expandable title="Optional Fields">
      <ResponseField name="Add a Note" type="text">
        Include an internal note for your team. This note is only visible within Pipedrive and helps with tracking and context.
      </ResponseField>

      <ResponseField name="Select Labels" type="tags">
        Assign labels to categorize and organize your communications for easier filtering and reporting.
      </ResponseField>
    </Expandable>

    <Note>
      At the top of the modal, you'll see your **most recent messages** with this contact (if any previous conversations exist), providing helpful context before sending.
    </Note>
  </Step>

  <Step title="Send the Message">
    1. Review all information carefully
    2. Click the **"Send Template"** button at the bottom of the modal
    3. Your message will be sent immediately

    <Check>
      Message sent successfully!
    </Check>

    <Frame>
      <img alt="Send Template Modal" />
    </Frame>
  </Step>
</Steps>

## Sending Messages from Contacts

The process for sending WhatsApp messages from contacts is nearly identical to sending from deals, with minor differences noted below.

### Accessing the Whatsable Integration Panel

<Steps>
  <Step title="Navigate to Contacts">
    1. Go to your **Pipedrive Dashboard**
    2. Navigate to the **Contacts** menu
    3. Select your desired **Contact**
  </Step>

  <Step title="Locate the Integration Panel">
    1. On the right-hand panel, scroll down past the Summary section
    2. Find the **Whatsable Integration** section

    <Frame>
      <img alt="Whatsable Integration Panel" />
    </Frame>
  </Step>
</Steps>

### Understanding the Integration Panel

The Whatsable Integration panel displays the same connection information as in deals:

<CardGroup>
  <Card title="Whatsable License Status" icon="circle-check">
    Confirms your subscription is active
  </Card>

  <Card title="Synced WhatsApp Account" icon="link">
    Shows which WhatsApp Business account is connected
  </Card>

  <Card title="WhatsApp Connection Status" icon="signal-bars">
    Indicates if your WhatsApp connection is active
  </Card>

  <Card title="Last WhatsApp Communication" icon="clock">
    Displays the date and time of the most recent message
  </Card>

  <Card title="Whatsable Chat URL" icon="arrow-up-right-from-square">
    Provides a direct link to the conversation
  </Card>
</CardGroup>

### Sending Options

The same three options are available:

<CardGroup>
  <Card title="Live Chat" icon="messages">
    Opens the Whatsable chat interface directly within Pipedrive
  </Card>

  <Card title="Send Scheduled Message" icon="clock">
    Schedule a message for a specific date and time
  </Card>

  <Card title="Send Template" icon="paper-plane">
    Send a template message immediately
  </Card>
</CardGroup>

<Info>
  **Key Difference**: Phone numbers are pulled from the contact's information rather than deal-specific numbers. All other fields and processes remain identical to sending from deals.
</Info>

## Best Practices

<AccordionGroup>
  <Accordion title="Verify Connection Status" icon="shield-check">
    **Before Sending Messages**

    Always check that your WhatsApp connection shows as ACTIVE before attempting to send messages to avoid delivery failures.
  </Accordion>

  <Accordion title="Review Templates" icon="file-lines">
    **Template Management**

    * Ensure your message templates are up-to-date in the Notifyer dashboard
    * Test templates with yourself before using them with customers
    * Create templates in advance for different scenarios
  </Accordion>

  <Accordion title="Double-Check Phone Numbers" icon="phone">
    **Phone Number Verification**

    * Confirm the recipient's phone number is correct
    * Verify the number includes the country code (e.g., +1 for US)
    * Update contact information if numbers are missing or incorrect
  </Accordion>

  <Accordion title="Use Labels Consistently" icon="tags">
    **Message Organization**

    * Develop a clear labeling system for easier tracking
    * Apply consistent labels across your team
    * Use labels for reporting and analytics purposes
  </Accordion>

  <Accordion title="Add Internal Notes" icon="note-sticky">
    **Documentation Best Practices**

    * Document the purpose of each message for future reference
    * Include context that will help team members understand the communication
    * Keep notes concise but informative
  </Accordion>

  <Accordion title="Review Recent Messages" icon="message-lines">
    **Maintain Context**

    * Always check conversation history before sending new messages
    * Avoid sending duplicate or redundant information
    * Ensure message continuity for better customer experience
  </Accordion>

  <Accordion title="Schedule Strategically" icon="calendar-clock">
    **Timing Considerations**

    * Consider your recipient's timezone when scheduling messages
    * Avoid sending messages during off-hours or weekends unless necessary
    * Set reminders to follow up if no response is received
  </Accordion>

  <Accordion title="Create Clear Variable Names" icon="input-text">
    **Template Creation**

    * Make placeholder fields intuitive for anyone on your team
    * Use descriptive variable names (e.g., customer\_name, order\_date)
    * Test variable population before mass sending
  </Accordion>
</AccordionGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion title="WhatsApp Connection Shows as INACTIVE" icon="circle-exclamation">
    <Steps>
      <Step title="Reconnect WhatsApp Account">
        Reconnect your WhatsApp Business account in the Whatsable dashboard
      </Step>

      <Step title="Verify Configuration">
        Verify your WhatsApp Business account is properly configured
      </Step>

      <Step title="Contact Support">
        Contact Whatsable support if the issue persists after reconnection
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="No Templates Available in Dropdown" icon="empty-set">
    <Steps>
      <Step title="Create Templates">
        Create templates in the Notifyer by Whatsable dashboard first
      </Step>

      <Step title="Check Approval Status">
        Ensure templates are approved by WhatsApp (if required for your template type)
      </Step>

      <Step title="Refresh Page">
        Refresh your Pipedrive page after creating new templates to see them appear
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Scheduled Message Not Sent" icon="clock-rotate-left">
    <Steps>
      <Step title="Check Connection Status">
        Verify your WhatsApp connection was active at the scheduled time
      </Step>

      <Step title="Verify Timezone">
        Check that the timezone was set correctly when scheduling
      </Step>

      <Step title="Review Message Logs">
        Review the message logs in Whatsable for error details and delivery status
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Phone Number Not Appearing" icon="phone-slash">
    <Steps>
      <Step title="Verify Phone Number Exists">
        Ensure the contact or deal has a valid phone number in Pipedrive
      </Step>

      <Step title="Check Format">
        Verify the phone number format includes the country code (e.g., +1234567890)
      </Step>

      <Step title="Update Contact">
        Update the contact information if the phone number is missing or incorrect
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Template Variables Not Populating" icon="brackets-curly">
    <Steps>
      <Step title="Check Variable Names">
        Ensure variable names in your template match the fields you're filling
      </Step>

      <Step title="Verify Data Source">
        Confirm the data source (contact or deal) has the required information
      </Step>

      <Step title="Test Template">
        Send a test message to yourself to verify variable population before sending to customers
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Message Delivery Failed" icon="triangle-exclamation">
    <Steps>
      <Step title="Verify Recipient Number">
        Confirm the recipient has an active WhatsApp account on that number
      </Step>

      <Step title="Check Message Content">
        Ensure your message complies with WhatsApp's business messaging policies
      </Step>

      <Step title="Review Credits">
        Verify your Whatsable account has sufficient credits or an active subscription
      </Step>

      <Step title="Contact Support">
        If issues persist, contact Whatsable support with the message details
      </Step>
    </Steps>
  </Accordion>
</AccordionGroup>

<Info>
  For more information about template creation and management, visit the Notifyer by Whatsable dashboard or contact our support team.
</Info>

## Need help?

Our support team is ready to assist you:

<CardGroup>
  <Card title="Email support" icon="envelope" href="mailto:team@whatsable.app">
    Contact [team@whatsable.app](mailto:team@whatsable.app)
  </Card>

  <Card title="Schedule a demo" icon="calendar" href="https://tidycal.com/axelmeta/notifyer-systems-demo">
    Book a personalized walkthrough
  </Card>

  <Card title="Live chat" icon="message-dots" href="">
    Click the green chat button in the bottom right corner of the Notifyer System dashboard
  </Card>
</CardGroup>

<Info>
  For additional automation platform integrations and advanced configurations, please contact our support team or check our integration documentation.
</Info>


# Zapier
Source: https://docs.whatsable.app/guides/notifier-system/zapier-overview

Learn how to seamlessly integrate Zapier with the Notifyer System for enterprise-level WhatsApp automation

# Notifyer System Integration with Zapier

<Frame>
  <img />
</Frame>

<Tip>
  This guide walks you through connecting Notifyer System with Zapier to create powerful automated WhatsApp messaging workflows for your business
</Tip>

## Prerequisites

Before getting started, make sure you have:

<CardGroup>
  <Card title="Notifyer System Account" icon="user">
    Active Notifyer System account with a subscription plan (Monthly or Pay-as-you-go)
  </Card>

  <Card title="Zapier Account" icon="user">
    Access to [Zapier](https://zapier.com/sign-up/) workflow automation platform
  </Card>
</CardGroup>

<Tip>
  New to Notifyer System? [Sign up here](https://console.notifyer-systems.com/)
</Tip>

## Setting up your Notifyer System account

<Steps>
  <Step title="Complete the Embedding Process">
    Before sending WhatsApp messages, you must complete the platform embedding process, which connects your WhatsApp Business account to Notifyer System.

    <Info>
      The embedding process is required by Meta to ensure proper business verification and compliance with WhatsApp Business Platform policies.
    </Info>
  </Step>

  <Step title="Set up message templates">
    Notifyer System provides two methods for sending WhatsApp messages:

    <Accordion title="Option A: Template messages">
      <p>WhatsApp templates are pre-approved message formats that allow for personalization while maintaining compliance with WhatsApp policies.</p>

      <Steps>
        <Step title="Navigate to Templates">
          Go to **Your Templates** in your Notifyer dashboard
        </Step>

        <Step title="Create Template">
          Click the **Create Template** tab at the top of the page
        </Step>

        <Step title="Fill out the form">
          Complete the template creation form with the following details:

          <ResponseField name="Template Name" type="string">
            Choose a descriptive name for internal reference
          </ResponseField>

          <ResponseField name="Language" type="string">
            Choose your template's primary language
          </ResponseField>

          <ResponseField name="Category" type="string">
            Select the appropriate message category
          </ResponseField>

          <ResponseField name="Header" type="image | document | video">
            Optional: Add an image, document, or video header
          </ResponseField>

          <ResponseField name="Message Body" type="string">
            Craft your message content
          </ResponseField>

          <ResponseField name="Variables" type="string">
            Add placeholders using `{{1}}`, `{{2}}` format for personalization
          </ResponseField>

          <ResponseField name="Buttons" type="button">
            Optional: Configure call-to-action buttons
          </ResponseField>
        </Step>

        <Step title="Submit for review">
          Click **Preview and Submit**
        </Step>
      </Steps>

      <Frame>
        <img alt="Template Creation Interface" />
      </Frame>

      <Warning>
        Templates typically get reviewed within 24 hours. Creating compliant templates that avoid promotional language increases approval chances.
      </Warning>
    </Accordion>

    <Accordion title="Option B: Non-template messages">
      <p>For simpler communications, you can send non-template messages that include:</p>

      <CardGroup>
        <Card title="Text" icon="message-text">
          Plain text messages within the 24-hour window
        </Card>

        <Card title="Images" icon="image">
          Photos and graphics in supported formats
        </Card>

        <Card title="Documents" icon="file-pdf">
          PDFs, Word docs, and other file types
        </Card>

        <Card title="Videos" icon="video">
          MP4 and other supported video formats
        </Card>
      </CardGroup>

      <Note>
        Non-template messages can only be sent within the 24-hour customer service window after a customer initiates contact with your business.
      </Note>
    </Accordion>
  </Step>

  <Step title="Get your API key">
    To connect Notifyer System with Zapier, you'll need an API key:

    1. In your Notifyer dashboard, navigate to [**API Keys**](https://console.notifyer-systems.com/api-key)
    2. Copy your unique API key
    3. Store it securely—you'll need it for the integration

    <Warning>
      Never share your API key publicly or commit it to version control systems.
    </Warning>

    <Frame>
      <img alt="API Key Location" />
    </Frame>
  </Step>
</Steps>

## Connect Notifyer System to Zapier

Now that you have your Notifyer System account configured, let's connect it to Zapier to automate your messaging workflows.

<Steps>
  <Step title="Connect Notifyer System to Zapier">
    1. Log in to your Zapier account
    2. Navigate to Notifyer System dashboard and select **Connect to Zapier** in the side menu
    3. Click **Continue** in the connection guide popup
    4. Click **Accept & Build a Zap** on the invitation page

    <Check>
      You're now ready to create Zaps with the Notifyer System app
    </Check>

    <Frame>
      <img alt="Connecting Notifyer System to Zapier" />
    </Frame>
  </Step>

  <Step title="Set up your Zapier Zaps">
    1. Log in to your Zapier account
    2. Create a new workflow/Zap by clicking **+ Create** and select **Zaps**/**New Zap**
    3. Add a trigger step of your choice:
       * Popular triggers include Google Forms, Jotform, ClickUp, or a Schedule trigger
       * Connect and configure your trigger according to your use case

    <Frame>
      <img alt="Setting up Zapier Zaps" />
    </Frame>
  </Step>

  <Step title="Add the Notifyer System app">
    1. Select the next **Action** step or click the **+** button to add a new step
    2. Search for "Notifyer System" in the apps and tools library
    3. Select the app with the official Notifyer System logo

    <Frame>
      <img alt="Adding the Whatsable app" />
    </Frame>
  </Step>

  <Step title="Configure Notifyer System credentials">
    <Accordion title="Credential Setup">
      1. In the Notifyer System app Setup, select [**Send a WhatsApp Message with your template**](/guides/notifier-system/zapier-overview#template-messages) or [**Send WhatsApp Message Without Template**](/guides/notifier-system/zapier-overview#non-template-messages) in the **Action event** dropdown depending on your messaging needs
      2. Click **Sign In** in the **Account** field and you will be prompted to enter your API Key
      3. Enter your Notifyer System API key that you copied earlier
      4. Click **Yes, Continue to Notifyer System** to store your credential
      5. Next, click the **Continue** button in the Setup screen to proceed to the **Configure** section

      <Frame>
        <img alt="Configuring Notifyer System credentials" />
      </Frame>
    </Accordion>
  </Step>

  <Step title="Configure your message">
    Depending on your messaging needs, choose one of the following operations:

    <Tabs>
      <Tab title="Template Messages">
        <Steps>
          <Step title="Select Action event">
            In the **Setup** section, select **Send a WhatsApp Message with your template** in the **Action event** dropdown and continue to the **Configure** section
          </Step>

          <Step title="Configure message">
            Complete the required fields in the **Configure** section:

            <ResponseField name="Template" type="string">
              Select from your pre-approved templates in the dropdown
            </ResponseField>

            <ResponseField name="Phone Number" type="string">
              Enter the recipient's phone number with country code (e.g., +14155552671) or use dynamic data from previous nodes
            </ResponseField>

            <ResponseField name="Note" type="string">
              Add note for internal tracking. This data won't be sent to the recipient
            </ResponseField>

            <ResponseField name="Labels" type="multiselect">
              Select label(s) for internal tracking. This data won't be sent to the recipient
            </ResponseField>

            <ResponseField name="Media" type="string">
              Enter publicly accessible media URL for Media (image/video/document) header.

              <Info>
                This field will only appear if you have a Media (image/video/document) header configured in your selected template.
              </Info>
            </ResponseField>

            <ResponseField name="Body ()" type="string">
              Fill in values for each Body(s) in your template, mapping them to dynamic data when applicable
            </ResponseField>

            <ResponseField name="Button(s)" type="string">
              Fill in values for each button in your template, mapping them to dynamic data when applicable.

              <Info>
                This field(s) will only appear if you have configured button(s) in your selected template. You will see the button name as the field name.
              </Info>
            </ResponseField>
          </Step>

          <Step title="Complete message details">
            Based on your selected message type, fill in the required fields:

            * For text messages: Enter your message content
            * For media messages: Provide a publicly accessible URL to your file
            * Optional caption (for media files)
          </Step>
        </Steps>

        <Frame>
          <img alt="Template Message Configuration" />
        </Frame>
      </Tab>

      <Tab title="Non-Template Messages">
        <Steps>
          <Step title="Select operation">
            In the **Operation Name or ID** dropdown, select **Send Non Template Message**
          </Step>

          <Step title="Enter phone number">
            Enter the **Phone Number** with country code
          </Step>

          <Step title="Select message type">
            Choose from the following message types:

            <CardGroup>
              <Card title="Text Message" icon="message">
                For plain text messages
              </Card>

              <Card title="Document Message" icon="file">
                For sending documents (PDF, Word, etc.)
              </Card>

              <Card title="Image Message" icon="image">
                For sending images (JPEG, PNG, etc.)
              </Card>

              <Card title="Video Message" icon="video">
                For sending videos (MP4, 3GP, etc.)
              </Card>
            </CardGroup>
          </Step>

          <Step title="Complete message details">
            Based on your selected message type, fill in the required fields:

            * For text messages: Enter your message content
            * For media messages: Provide a publicly accessible URL to your file
            * Optional caption (for media files)
          </Step>
        </Steps>

        <Warning>
          For all media types, ensure your file URLs are publicly accessible and match the supported file formats.
        </Warning>

        <Frame>
          <img alt="Non-Template Message Configuration" />
        </Frame>
      </Tab>
    </Tabs>
  </Step>

  <Step title="Test and activate your Zap">
    1. Click **Continue** and then click **Test step** in the **Test** to verify it's working correctly
    2. If the test is successful, you'll see a confirmation message
    3. Click **Publish** to save your entire Zap
    4. Toggle the **Active** switch in the top-left corner to activate your Zap
  </Step>
</Steps>

## Example use cases

<CardGroup>
  <Card title="Customer Onboarding" icon="user-plus">
    Send a welcome message when a new customer signs up
  </Card>

  <Card title="Order Notifications" icon="box-check">
    Update customers when their order status changes
  </Card>

  <Card title="Appointment Reminders" icon="calendar">
    Automatically send reminders before scheduled appointments
  </Card>

  <Card title="Lead Follow-up" icon="user-check">
    Send personalized messages to new leads from your form submissions
  </Card>

  <Card title="Support Ticket Updates" icon="ticket">
    Notify customers when their support ticket status changes
  </Card>
</CardGroup>

## Workflow Diagram

<Frame>
  ```mermaid theme={null}
  flowchart LR
    A[Trigger Step] --> B[Data Transformation]
    B --> C[Notifyer System App]
    C --> D{Message Sent?}
    D -->|Yes| E[Success Path]
    D -->|No| F[Error Handling]
    E --> G[Additional Actions]
    F --> H[Retry Logic]
  ```
</Frame>

## Example use cases

<CardGroup>
  <Card title="Order confirmations" icon="box-check">
    Send automatic order confirmations when new orders are placed
  </Card>

  <Card title="Appointment reminders" icon="calendar">
    Schedule reminders before upcoming appointments
  </Card>

  <Card title="Lead notifications" icon="user-plus">
    Alert your sales team when new leads come in
  </Card>

  <Card title="Customer support" icon="headset">
    Route support inquiries to the appropriate team member
  </Card>

  <Card title="Delivery updates" icon="truck">
    Keep customers informed about their delivery status
  </Card>

  <Card title="Payment reminders" icon="credit-card">
    Send automatic payment reminders for overdue accounts
  </Card>
</CardGroup>

## Best practices

<AccordionGroup>
  <Accordion title="Test thoroughly" icon="vial">
    Always test your workflows with test phone numbers before activating them for production use.
  </Accordion>

  <Accordion title="Use templates" icon="file-lines">
    Whenever possible, use pre-approved templates for better deliverability and compliance.
  </Accordion>

  <Accordion title="Add personalization" icon="user">
    Include customer names and specific details to increase engagement and response rates.
  </Accordion>

  <Accordion title="Follow WhatsApp policies" icon="shield-check">
    Ensure all message content complies with WhatsApp Business policies to avoid account restrictions.
  </Accordion>

  <Accordion title="Monitor performance" icon="chart-line">
    Regularly check your message delivery rates in your Notifyer dashboard.
  </Accordion>
</AccordionGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Messages not sending?" icon="circle-exclamation">
    <Steps>
      <Step title="Verify API key">
        Ensure your API key is entered correctly in the Zapier credentials
      </Step>

      <Step title="Check phone numbers">
        Confirm phone numbers are in the correct international format (e.g., +14155552671)
      </Step>

      <Step title="Check subscription">
        Verify your Notifyer subscription is active and has available credits
      </Step>

      <Step title="Template verification">
        For template messages, ensure you're using an approved template
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Template errors?" icon="file-exclamation">
    <Steps>
      <Step title="Variable check">
        Verify all required variables are included in your template message
      </Step>

      <Step title="Format verification">
        Check that variable formats match the expected values (text, number, date, etc.)
      </Step>

      <Step title="Template name">
        Ensure you're using the correct template name exactly as it appears in your dashboard
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Media not displaying?" icon="image">
    <Steps>
      <Step title="URL access">
        Confirm your media URLs are publicly accessible (test in an incognito browser)
      </Step>

      <Step title="File format">
        Verify the file format is supported by WhatsApp
      </Step>

      <Step title="File size">
        Check that file sizes are within WhatsApp limits:

        * Images: up to 5MB
        * Videos: up to 16MB
        * Documents: up to 100MB
      </Step>
    </Steps>
  </Accordion>
</AccordionGroup>

## Need help?

Our support team is ready to assist you:

<CardGroup>
  <Card title="Email support" icon="envelope" href="mailto:team@whatsable.app">
    Contact [team@whatsable.app](mailto:team@whatsable.app)
  </Card>

  <Card title="Schedule a demo" icon="calendar" href="https://tidycal.com/axelmeta/notifyer-systems-demo">
    Book a personalized walkthrough
  </Card>

  <Card title="Live chat" icon="message-dots" href="">
    Click the green chat button in the bottom right corner of the Notifyer System dashboard
  </Card>
</CardGroup>

<Info>
  For additional automation platform integrations (Make.com, n8n, etc.), please contact our support team or check our integration documentation.
</Info>


# Message Analytics
Source: https://docs.whatsable.app/guides/notifier/advanced/analytics

Learn how to track and analyze your WhatsApp messages with Notifier by Whatsable

# Message Analytics

Track and analyze your WhatsApp messaging performance with comprehensive analytics.

## Key Metrics

### Message Performance

* Delivery rates
* Read rates
* Response rates
* Response times
* Error rates

### Template Performance

* Usage by template
* Success rates
* Response patterns
* Conversion rates
* Cost per message

### User Engagement

* Active users
* Message frequency
* Response patterns
* User segments
* Retention rates

## Analytics Dashboard

### Real-time Monitoring

```javascript theme={null}
// Example: Track message status
app.post('/webhook/message-status', async (req, res) => {
  const { message_id, status, timestamp } = req.body;
  
  await updateMessageStatus({
    message_id,
    status,
    timestamp,
    metrics: {
      delivery_time: calculateDeliveryTime(message_id),
      response_time: calculateResponseTime(message_id)
    }
  });
});
```

### Custom Reports

```javascript theme={null}
// Example: Generate daily report
async function generateDailyReport() {
  const report = {
    date: new Date(),
    metrics: {
      total_messages: await getTotalMessages(),
      delivered_messages: await getDeliveredMessages(),
      read_messages: await getReadMessages(),
      response_rate: await calculateResponseRate(),
      average_response_time: await calculateAverageResponseTime()
    },
    templates: await getTemplatePerformance(),
    errors: await getErrorSummary()
  };
  
  return report;
}
```

## Data Export

### Export Formats

* CSV
* JSON
* Excel
* PDF
* API endpoints

### Export Options

* Date range
* Metrics selection
* Template filtering
* User segmentation
* Custom fields

## Best Practices

### Data Collection

* Track all relevant metrics
* Use consistent naming
* Validate data quality
* Store historical data
* Implement data retention

### Analysis

* Set clear KPIs
* Monitor trends
* Compare performance
* Identify patterns
* Make data-driven decisions

## Integration

### Third-party Tools

* Google Analytics
* Mixpanel
* Amplitude
* Custom dashboards
* Business intelligence tools

### API Access

```javascript theme={null}
// Example: Fetch analytics data
const getAnalytics = async (params) => {
  const response = await axios.get(
    'https://api.insightssystem.com/api:-GWQv5aM/analytics',
    {
      params,
      headers: {
        'Authorization': `Bearer ${process.env.NOTIFIER_API_KEY}`
      }
    }
  );
  return response.data;
};
```

## Next Steps

* Learn about [Templates](/guides/notifier/advanced/templates)
* Explore [Automation](/guides/notifier/advanced/automation)
* Check out our [API Reference](/api-reference/notifier)
* Read our [Getting Started](/guides/notifier/getting-started) guide


# Message Automation
Source: https://docs.whatsable.app/guides/notifier/advanced/automation

Learn how to automate your WhatsApp messages with Notifier by Whatsable

# Message Automation

Automate your WhatsApp messaging workflows to save time and improve efficiency.

## Workflow Types

### Event-Based Triggers

```javascript theme={null}
// Example: Send welcome message on user signup
app.post('/webhook/signup', async (req, res) => {
  const { user } = req.body;
  
  await sendTemplateMessage({
    to: user.phone,
    template: 'welcome_message',
    variables: {
      name: user.name,
      company: 'Acme Inc'
    }
  });
});
```

### Scheduled Messages

```javascript theme={null}
// Example: Send appointment reminder
const schedule = require('node-schedule');

schedule.scheduleJob('0 9 * * *', async () => {
  const appointments = await getTodaysAppointments();
  
  for (const appointment of appointments) {
    await sendTemplateMessage({
      to: appointment.patient.phone,
      template: 'appointment_reminder',
      variables: {
        name: appointment.patient.name,
        time: appointment.time,
        doctor: appointment.doctor.name
      }
    });
  }
});
```

## Automation Features

### Conditional Logic

* If/else conditions
* Switch statements
* Multiple conditions
* Nested conditions

### Workflow Steps

1. Trigger
2. Conditions
3. Actions
4. Delays
5. Notifications

### Integration Points

* Webhooks
* API endpoints
* Database triggers
* Third-party services

## Best Practices

### Workflow Design

* Keep workflows simple
* Use clear naming conventions
* Document your workflows
* Test thoroughly
* Monitor performance

### Error Handling

* Implement retry logic
* Set up error notifications
* Log all actions
* Handle timeouts
* Validate inputs

## Monitoring

Track your automated workflows:

* Success rates
* Error rates
* Response times
* Resource usage
* Cost analysis

## Next Steps

* Learn about [Templates](/guides/notifier/advanced/templates)
* Explore [Analytics](/guides/notifier/advanced/analytics)
* Check out our [API Reference](/api-reference/notifier)
* Read our [Getting Started](/guides/notifier/getting-started) guide


# Message Templates
Source: https://docs.whatsable.app/guides/notifier/advanced/templates

Learn how to use and manage message templates in Notifier by Whatsable

# Message Templates

Message templates are pre-approved message formats that you can use to send WhatsApp messages to your customers.

## Template Types

### Text Templates

```json theme={null}
{
  "name": "welcome_message",
  "language": "en",
  "category": "UTILITY",
  "components": [
    {
      "type": "BODY",
      "text": "Welcome to {{company}}! We're excited to have you on board, {{name}}."
    }
  ]
}
```

### Media Templates

```json theme={null}
{
  "name": "product_announcement",
  "language": "en",
  "category": "MARKETING",
  "components": [
    {
      "type": "HEADER",
      "format": "IMAGE",
      "example": {
        "header_url": ["https://example.com/image.jpg"]
      }
    },
    {
      "type": "BODY",
      "text": "Check out our new product: {{product_name}}! Only {{price}} for a limited time."
    },
    {
      "type": "BUTTON",
      "sub_type": "URL",
      "index": "0",
      "parameters": [
        {
          "type": "text",
          "text": "Shop Now"
        }
      ]
    }
  ]
}
```

## Template Management

### Creating Templates

1. Go to the Templates section in your dashboard
2. Click "Create New Template"
3. Choose the template type
4. Add your content and variables
5. Submit for approval

### Template Variables

* Use `{{variable_name}}` syntax
* Variables are case-sensitive
* Maximum 10 variables per template
* Supported types: text, currency, date, time

### Best Practices

* Keep templates concise
* Use clear variable names
* Test templates before submission
* Monitor template performance
* Update templates regularly

## Template Analytics

Track your template performance:

* Delivery rates
* Response rates
* Conversion rates
* User engagement
* Error rates

## Next Steps

* Learn about [Automation](/guides/notifier/advanced/automation)
* Explore [Analytics](/guides/notifier/advanced/analytics)
* Check out our [API Reference](/api-reference/notifier)
* Read our [Getting Started](/guides/notifier/getting-started) guide


# API Documentation
Source: https://docs.whatsable.app/guides/notifier/api-documentation

Notifier by Whatsable API Documentation

# API

# 📚 Notifier by Whatsable API Documentation

<div>
  <p>
    Welcome to the <span>Notifier by Whatsable API Documentation</span>! This guide provides comprehensive details on how to use the <span>Notifier API</span> to send WhatsApp messages programmatically. Below, you'll find information on the API endpoint, authentication, request and response structures, error handling, and supported attachment types.
  </p>
</div>

***

## 🚀 API Overview

<div>
  The <span>Notifier API</span> allows you to send WhatsApp messages, including text and attachments, to customers. It's designed to be simple and easy to integrate into your applications or workflows.
</div>

***

## 📌 API Endpoint

<div>
  * **POST**: `https://api.insightssystem.com/api:-GWQv5aM/send`
</div>

***

## 🔑 Authentication

<div>
  To use the API, you need to include an <span>Authorization Token</span> in the request headers. The token must be prefixed with <span>Bearer</span>.

  ### Headers

  * `Content-Type`: `application/json`
  * `Authorization`: `Bearer YOUR_TOKEN_HERE`
</div>

***

## 📤 Request Payload

<div>
  The request body should be a JSON object with the following fields:

  | Field | Type | Description |
  | - | - | - |
  | `phone` | String | The recipient's phone number in **international format** (e.g., `+1234567890`). |
  | `text` | String | The message content you want to send. |
  | `attachment` | String | (Optional) A public URL to an attachment (e.g., image, PDF, video). |
  | `filename` | String | (Optional) The name of the attachment file. |

  ### Example Request Body

  <div>
    ```json theme={null}
    {
      "phone": "+1234567890",
      "text": "Hello, this is a test message from Notifier!",
      "attachment": "https://example.com/image.jpg",
      "filename": "image.jpg"
    }
    ```
  </div>
</div>

***

## 📥 Response Structure

<div>
  The API responds with a JSON object. Below are examples of <span>success</span> and <span>error</span> responses.

  ### Success Response

  <div>
    ```json theme={null}
    {
      "message": "Message sent successfully"
    }
    ```
  </div>

  ### Error Response

  <div>
    ```json theme={null}
    {
      "message": "Message sending failed | Reason: Message limit for this number reached."
    }
    ```
  </div>
</div>

***

## 🛠️ Error Handling

<div>
  The API provides detailed error messages to help you troubleshoot issues. Common errors include:

  1. <span>Invalid Phone Number</span>: Ensure the phone number is in <span>E.164 format</span>.
  2. <span>Message Limit Reached</span>: You've exceeded the allowed number of messages for a specific phone number.
  3. <span>Attachment Issues</span>: Ensure the attachment URL is public and accessible.
  4. <span>Authentication Failure</span>: Verify that the `Authorization` token is correct.
  5. <span>Insufficient Credits</span>: Your account balance is insufficient to send the message.
  6. <span>Subscription Expired</span>: Your subscription has ended, and you need to renew it.
  7. <span>Rate Limit Exceeded</span>: You've exceeded the allowed number of messages per minute or hour.
  8. <span>Unique Number Limit Reached</span>: You've reached the limit of unique phone numbers you can message.
  9. <span>File Size or Type Error</span>: The attachment does not meet WhatsApp's size or type requirements.
  10. <span>No WhatsApp Account</span>: The recipient does not have an active WhatsApp account.
</div>

***

## 📋 Code Examples

<div>
  ### 1. cURL

  <div>
    ```bash theme={null}
    curl -X POST https://api.insightssystem.com/api:-GWQv5aM/send \
    -H "Content-Type: application/json" \
    -H "Authorization: Bearer YOUR_TOKEN_HERE" \
    -d '{
      "phone": "+1234567890",
      "text": "Hello, this is a test message from Notifier!",
      "attachment": "https://example.com/image.jpg",
      "filename": "image.jpg"
    }'
    ```
  </div>

  ### 2. JavaScript (Fetch API)

  <div>
    ```javascript theme={null}
    fetch("https://api.insightssystem.com/api:-GWQv5aM/send", {
      method: "POST",
      headers: {
        "Content-Type": "application/json",
        Authorization: "Bearer YOUR_TOKEN_HERE",
      },
      body: JSON.stringify({
        phone: "+1234567890",
        text: "Hello, this is a test message from Notifier!",
        attachment: "https://example.com/image.jpg",
        filename: "image.jpg",
      }),
    })
      .then((response) => response.json())
      .then((data) => console.log(data))
      .catch((error) => console.error(error));
    ```
  </div>

  ### 3. Python (Requests Library)

  <div>
    ```python theme={null}
    import requests
    import json

    url = "https://api.insightssystem.com/api:-GWQv5aM/send"
    headers = {
        "Content-Type": "application/json",
        "Authorization": "Bearer YOUR_TOKEN_HERE"
    }
    payload = {
        "phone": "+1234567890",
        "text": "Hello, this is a test message from Notifier!",
        "attachment": "https://example.com/image.jpg",
        "filename": "image.jpg"
    }

    response = requests.post(url, headers=headers, data=json.dumps(payload))
    print(response.json())
    ```
  </div>

  ### 4. Go

  <div>
    ```go theme={null}
    package main

    import (
    	"bytes"
    	"fmt"
    	"net/http"
    )

    func main() {
    	url := "https://api.insightssystem.com/api:-GWQv5aM/send"
    	payload := []byte(`{
    		"phone": "+1234567890",
    		"text": "Hello, this is a test message from Notifier!",
    		"attachment": "https://example.com/image.jpg",
    		"filename": "image.jpg"
    	}`)

    	req, err := http.NewRequest("POST", url, bytes.NewBuffer(payload))
    	if err != nil {
    		fmt.Println("Error creating request:", err)
    		return
    	}

    	req.Header.Set("Content-Type", "application/json")
    	req.Header.Set("Authorization", "Bearer YOUR_TOKEN_HERE")

    	client := &http.Client{}
    	resp, err := client.Do(req)
    	if err != nil {
    		fmt.Println("Error sending request:", err)
    		return
    	}
    	defer resp.Body.Close()

    	fmt.Println("Response Status:", resp.Status)
    }
    ```
  </div>

  ### 5. Java (HttpURLConnection)

  <div>
    ```java theme={null}
    import java.io.OutputStream;
    import java.net.HttpURLConnection;
    import java.net.URL;

    public class Main {
        public static void main(String[] args) {
            try {
                URL url = new URL("https://api.insightssystem.com/api:-GWQv5aM/send");
                HttpURLConnection conn = (HttpURLConnection) url.openConnection();
                conn.setRequestMethod("POST");
                conn.setRequestProperty("Content-Type", "application/json");
                conn.setRequestProperty("Authorization", "Bearer YOUR_TOKEN_HERE");
                conn.setDoOutput(true);

                String payload = "{\"phone\": \"+1234567890\", \"text\": \"Hello, this is a test message from Notifier!\", \"attachment\": \"https://example.com/image.jpg\", \"filename\": \"image.jpg\"}";

                try (OutputStream os = conn.getOutputStream()) {
                    byte[] input = payload.getBytes("utf-8");
                    os.write(input, 0, input.length);
                }

                int responseCode = conn.getResponseCode();
                System.out.println("Response Code: " + responseCode);
            } catch (Exception e) {
                e.printStackTrace();
            }
        }
    }
    ```
  </div>
</div>

***

## 📌 Attachment Support

<div>
  The <span>Notifier API</span> supports sending attachments with WhatsApp messages. Below are the supported file types and their size limits:

  ### Supported Media Types

  | **Media Type** | **File Extensions** | **MIME Types** | **Max Size** |
  | - | - | - | - |
  | **Images** | `.jpeg`, `.png` | `image/jpeg`, `image/png` | 5 MB |
  | **Videos** | `.mp4`, `.3gp` | `video/mp4`, `video/3gpp` | 16 MB |
  | **Documents** | `.pdf`, `.doc`, `.xls`, `.ppt`, `.txt` | `application/pdf`, `application/msword`, `application/vnd.ms-excel`, `application/vnd.ms-powerpoint`, `text/plain` | 100 MB |
  | **Audio** | `.mp3`, `.aac`, `.m4a`, `.ogg` | `audio/mpeg`, `audio/aac`, `audio/mp4`, `audio/ogg` | 16 MB |
</div>

***

## 📌 Key Points to Remember

<div>
  * **Phone Number Format**: Always use the **E.164 format** (e.g., `+1234567890`).
  * **Attachment URL**: Ensure the attachment URL is public and accessible.
  * **Authorization Token**: Include the `Bearer` token in the `Authorization` header.
  * **Error Handling**: Check the `message` field in the response for detailed error information.
  * **Line Break**: In the message for line break or for starting a new line, `\n` needs to be added before the new line. Example:

  Input:
  `Hi there,\nThis is John from Acme Co.`

  Output:
  Hi there,
  This is John from Acme Co.
</div>

***

## ❓ Need Help?

<div>
  If you encounter any issues or need further assistance, feel free to reach out to our support team:

  * **Email Support**: [support@whatsable.app](mailto:support@whatsable.app)
  * **Documentation**: [Notifier API Documentation](https://www.notion.so/Documentation-for-Whatsable-Notifier-API-871f707adcd1451bb437f47db27e8abb?pvs=21)
</div>

***

<div>
  <h2>🚀 Start Sending WhatsApp Messages Today!</h2>

  <div>
    <a href="https://notifier.whatsable.app/">
      Sign Up for Notifier by Whatsable
    </a>
  </div>
</div>

***

**Disclaimer**: This service is not affiliated with nor endorsed by WhatsApp Inc. The tool uses the WhatsApp API but is not affiliated with WhatsApp.


# Notifier by Whatsable Features
Source: https://docs.whatsable.app/guides/notifier/features

Explore the advanced features of Notifier by Whatsable

# Notifier by Whatsable Features

Notifier by Whatsable provides a comprehensive set of features for complex WhatsApp messaging needs.

## Core Features

### Message Types

* Text messages
* Media messages (images, documents, audio, video)
* Location sharing
* Contact sharing
* Interactive messages
* List messages
* Button messages

### Message Management

* Message status tracking
* Delivery receipts
* Read receipts
* Message history
* Message templates
* Bulk messaging
* Scheduled messages

### Security

* End-to-end encryption
* API key authentication
* Rate limiting
* IP whitelisting
* Two-factor authentication
* Audit logs

## Advanced Features

### Templates

* Pre-approved message templates
* Dynamic variables
* Multi-language support
* Template analytics
* Template versioning

### Automation

* Workflow automation
* Conditional messaging
* Event-based triggers
* Custom webhooks
* Integration with third-party services

### Analytics

* Message delivery rates
* Response times
* User engagement
* Template performance
* Custom reports

## Best Practices

* Use approved templates
* Implement proper error handling
* Monitor message status
* Follow WhatsApp guidelines
* Regular template updates

## Next Steps

* Learn about [Integrations](/guides/notifier/integrations)
* Explore [Advanced Features](/guides/notifier/advanced/templates)
* Check out our [API Reference](/api-reference/notifier)
* Read our [Getting Started](/guides/notifier/getting-started) guide


# Getting Started with Notifier by Whatsable
Source: https://docs.whatsable.app/guides/notifier/getting-started

Learn how to get started with Notifier by Whatsable, the complex WhatsApp messaging solution

# Getting Started with Notifier by Whatsable

Notifier by Whatsable provides advanced WhatsApp messaging capabilities for businesses. This guide will help you get started with our complex solution.

## Prerequisites

* A WhatsApp Business account
* Understanding of API integration
* Your Notifier API key
* Basic knowledge of webhooks

## Quick Setup

1. Sign up for a Notifier by Whatsable account
2. Configure your WhatsApp Business account
3. Get your API key from the dashboard
4. Set up webhooks for message status updates

## First Message

Here's a quick example of sending your first message:

```bash theme={null}
curl -X POST https://api.insightssystem.com/api:-GWQv5aM/send \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+1234567890",
    "message": "Hello from Notifier by WhatsAble!",
    "template": "welcome_message",
    "variables": {
      "name": "John",
      "company": "Acme Inc"
    }
  }'
```

## Next Steps

* Learn about [Features](/guides/notifier/features)
* Explore [Integrations](/guides/notifier/integrations)
* Check out [Advanced Features](/guides/notifier/advanced/templates)
* Review our [API Reference](/api-reference/notifier)


# Notifier by Whatsable Integrations
Source: https://docs.whatsable.app/guides/notifier/integrations

Learn how to integrate Notifier by Whatsable with your applications

# Notifier by Whatsable Integrations

Integrate Notifier by Whatsable with your business tools and platforms.

## Available Integrations

### No-Code Platforms

* Zapier
* Make (formerly Integromat)
* n8n
* Pipedream
* Microsoft Power Automate

### CRM Systems

* Salesforce
* HubSpot
* Zoho CRM
* Pipedrive
* Microsoft Dynamics

### E-commerce Platforms

* Shopify
* WooCommerce
* Magento
* BigCommerce
* PrestaShop

### Marketing Tools

* Mailchimp
* ActiveCampaign
* Klaviyo
* SendGrid
* HubSpot Marketing

## Custom Integration

### REST API

```javascript theme={null}
const axios = require('axios');

const sendTemplateMessage = async (to, template, variables) => {
  try {
    const response = await axios.post(
      'https://api.insightssystem.com/api:-GWQv5aM/send',
      {
        to,
        template,
        variables
      },
      {
        headers: {
          'Authorization': `Bearer ${process.env.NOTIFIER_API_KEY}`,
          'Content-Type': 'application/json'
        }
      }
    );
    return response.data;
  } catch (error) {
    console.error('Error sending message:', error);
    throw error;
  }
};
```

### Webhooks

Configure webhooks to receive real-time updates:

```json theme={null}
{
  "event": "message.status",
  "data": {
    "message_id": "msg_123",
    "status": "delivered",
    "template": "welcome_message",
    "variables": {
      "name": "John",
      "company": "Acme Inc"
    },
    "timestamp": "2024-03-20T10:00:00Z"
  }
}
```

## Best Practices

* Use environment variables for API keys
* Implement retry logic with exponential backoff
* Handle rate limits appropriately
* Monitor webhook delivery
* Use template variables for dynamic content

## Next Steps

* Read our [Getting Started](/guides/notifier/getting-started) guide
* Explore [Features](/guides/notifier/features)
* Check out [Advanced Features](/guides/notifier/advanced/templates)
* Review our [API Reference](/api-reference/notifier)


# Make
Source: https://docs.whatsable.app/guides/notifier/make

Connect Notifier with Make to automate powerful WhatsApp messaging scenarios

# Notifier Integration with Make

<Frame>
  <img />
</Frame>

<Info>
  Notifier enables you to send automated WhatsApp messages through your favorite scenario automation tools. This guide walks you through integrating Notifier with Make to create powerful messaging scenarios
</Info>

## Prerequisites

Before getting started, make sure you have:

<CardGroup>
  <Card title="Notifier Account" icon="user">
    Active Notifier account with a subscription plan (Monthly or Pay-as-you-go)
  </Card>

  <Card title="Make Account" icon="user">
    Access to [Make](https://www.make.com/en/register/) scenario automation platform
  </Card>
</CardGroup>

<Tip>
  New to Notifier? [Sign up here](https://notifier.whatsable.app/)
</Tip>

## Set up your Notifier account

<Steps>
  <Step title="Configure your business information">
    First, let's set up your business profile in Notifier:

    1. Log in to your Notifier dashboard
    2. Navigate to **Business Information**
    3. Complete all required fields:
       * **Business Name**: Enter the name that will appear in messages sent to recipients
       * **Business Website or Social Media**: Add your website or social media URL
       * **Preferred Language**: Select the language for standard WhatsApp message elements
       * **Default Reply Text**: Create a template message that appears when recipients click "Reply"
       * **WhatsApp Number**: Add your business WhatsApp number where replies will be directed

    <Frame>
      <img alt="Configuring business information" />
    </Frame>

    <Note>
      After entering your WhatsApp number, Notifier will send a verification code to this number. Enter the code to verify ownership.
    </Note>

    Once saved, you'll see a preview of how your messages will appear to recipients. The actual message structure may vary slightly based on variables and attachments you include.
  </Step>

  <Step title="Get your API key">
    To connect Notifier with Make, you'll need your API key:

    1. In your Notifier dashboard, go to **API Keys**
    2. Copy your unique API key
    3. Store it securely—you'll need it for the integration

    <Warning>
      Never share your API key publicly or commit it to version control systems.
    </Warning>
  </Step>
</Steps>

## Connect Notifier to Make

Now that you have Notifier set up, let's connect it to Make to automate your scenarios.

<Steps>
  <Step title="Connect Notifier to Make">
    1. Log in to your Make account
    2. Navigate to Notifier dashboard and select **Connect to Make** in the side menu
    3. Click **Continue** in the connection guide popup
    4. Click **Install**, select your organization at the bottom of the screen, then click **Install** again. (Note: You need Admin, Owner, or App Developer role in your organization to install apps.)

    <Check>
      You're now ready to create scenarios with the Notifier app
    </Check>
  </Step>

  <Step title="Set up your Make Scenario">
    1. Log in to your Make account
    2. Create a new scenario by clicking **+ Create a new scenario**
    3. (Optional) Add a trigger module of your choice:
       * Popular triggers include Google Forms, Jotform, ClickUp, or a Schedule trigger
       * Connect and configure your trigger according to your use case

    <Frame>
      <img alt="Setting up Make module" />
    </Frame>
  </Step>

  <Step title="Add the Notifier module">
    1. Click the **+** button to add a new module
    2. Search for **Notifier Whatsable** in the apps or modules library
    3. Select the module with the official Notifer logo

    <Frame>
      <img alt="Adding the Notifier module" />
    </Frame>
  </Step>

  <Step title="Configure Notifier credentials">
    <Accordion title="Credential Setup">
      1. Once you click on Notifier module, select **Send a WhatsApp Message** from the **ACTIONS**
      2. Click **Create a connection** in the **Connection** section of Notifier module and you will be prompted to enter your API Key
      3. Enter your Notifier API key that you copied earlier
      4. Rename your connection name if needed
      5. Click **Save** to store your credential

      <Frame>
        <img alt="Configuring Notifier credentials" />
      </Frame>
    </Accordion>
  </Step>

  <Step title="Configure your message">
    Complete the required fields:

    <ResponseField name="Phone" type="string">
      Enter the recipient’s phone number (with country code) or use dynamic data from previous module (*Make sure that the phone number is valid and that you are only sending to one phone number per step.*)
    </ResponseField>

    <ResponseField name="Message Body" type="string">
      Type your message text or use variables from previous module
    </ResponseField>

    <Expandable title="Optional Parameters">
      <ResponseField name="File > Attachment URL (must be publicly available)" type="file">
        Enter public URL of a file, image, or video to send with your message
      </ResponseField>

      <ResponseField name="File Name" type="string">
        Specify a custom filename for your attachment
      </ResponseField>

      <ResponseField name="Additional Parameters" type="object">
        Customize advanced options as needed
      </ResponseField>
    </Expandable>

    <br />

    <Frame>
      <img alt="Configuring message" />
    </Frame>
  </Step>

  <Step title="Test and activate your scenario">
    1. Click **Save** to save your message configuration
    2. Right click on the Whatsable module and select **Run this module only** to verify the module is working correctly
       * or click **Run once** in the bottom-left corner of the screen to test the entire scenario
    3. If the test is successful, you'll see a confirmation message
    4. Click **Save** icon in the bottom-left corner to save your scenario (You can also set timer intarval for the scenario)
    5. Toggle the **Active** switch in the bottom-left corner with time to activate your scenario

    <Frame>
      <img alt="Testing and activating your scenario" />
    </Frame>
  </Step>
</Steps>

## Example use cases

<CardGroup>
  <Card title="Customer Onboarding" icon="user-plus">
    Send a welcome message when a new customer signs up
  </Card>

  <Card title="Order Notifications" icon="box-check">
    Update customers when their order status changes
  </Card>

  <Card title="Appointment Reminders" icon="calendar">
    Automatically send reminders before scheduled appointments
  </Card>

  <Card title="Lead Follow-up" icon="user-check">
    Send personalized messages to new leads from your form submissions
  </Card>

  <Card title="Support Ticket Updates" icon="ticket">
    Notify customers when their support ticket status changes
  </Card>
</CardGroup>

## Scenario Diagram

<Frame>
  ```mermaid theme={null}
  flowchart LR
    A[Trigger Module] --> B[Data Transformation]
    B --> C[Notifier Module]
    C --> D{Message Sent?}
    D -->|Yes| E[Success Path]
    D -->|No| F[Error Handling]
    E --> G[Additional Actions]
    F --> H[Retry Logic]
  ```
</Frame>

## Best practices

For optimal results when using Notifier with Make:

<AccordionGroup>
  <Accordion title="Personalize your messages" icon="user-check">
    Use data from previous modules in your workflow to create personalized, relevant messages for each recipient.
  </Accordion>

  <Accordion title="Keep messages concise" icon="text-size">
    Focus on a single call-to-action and keep your messages brief to maintain recipient engagement.
  </Accordion>

  <Accordion title="Test thoroughly" icon="flask">
    Always run complete tests of your workflow before deploying to production to catch any potential issues.
  </Accordion>

  <Accordion title="Monitor performance" icon="chart-line">
    Regularly check your Notifier dashboard to monitor delivery rates and optimize your messaging strategy.
  </Accordion>

  <Accordion title="Respect privacy" icon="shield-check">
    Always provide clear opt-out instructions and respect recipient preferences regarding messaging.
  </Accordion>
</AccordionGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Message not being sent?" icon="circle-exclamation">
    <Steps>
      <Step title="Check account status">
        Verify that your Notifier account is active and has available credits
      </Step>

      <Step title="Verify business information">
        Ensure your business information is complete and properly verified
      </Step>

      <Step title="Confirm API key">
        Double-check that your API key is entered correctly in Make
      </Step>

      <Step title="Validate phone number">
        Confirm that the recipient's phone number is in the correct format (including country code)
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Formatting issues in messages?" icon="text-slash">
    <Steps>
      <Step title="Review template">
        Check your message template for any invalid characters or formatting issues
      </Step>

      <Step title="Variable formatting">
        Ensure variables from previous modules are properly formatted
      </Step>

      <Step title="Message length">
        Verify your message doesn't exceed WhatsApp's length limitations
      </Step>
    </Steps>
  </Accordion>
</AccordionGroup>

## Need help?

Our support team is ready to assist you:

<CardGroup>
  <Card title="Email support" icon="envelope" href="mailto:team@whatsable.app">
    Contact [team@whatsable.app](mailto:team@whatsable.app)
  </Card>

  <Card title="Schedule a demo" icon="calendar" href="https://tidycal.com/axelmeta/whatsapp-notifications-by-whatsable">
    Book a personalized walkthrough
  </Card>

  <Card title="Live chat" icon="message-dots" href="">
    Click the green chat button in the bottom right corner of the Notifier dashboard
  </Card>
</CardGroup>

<Info>
  For additional automation platform integrations (Zapier, n8n, etc.), please contact our support team or check our integration documentation.
</Info>


# n8n
Source: https://docs.whatsable.app/guides/notifier/n8n

Connect Notifier with n8n to automate powerful WhatsApp messaging workflows

# Notifier Integration with n8n

<Frame>
  <img />
</Frame>

<Info>
  Notifier enables you to send automated WhatsApp messages through your favorite workflow automation tools. This guide walks you through integrating Notifier with n8n to create powerful messaging workflows
</Info>

## Prerequisites

Before getting started, make sure you have:

<CardGroup>
  <Card title="Notifier Account" icon="user">
    Active Notifier account with a subscription plan (Monthly or Pay-as-you-go)
  </Card>

  <Card title="n8n Account" icon="user">
    Access to [n8n](https://app.n8n.cloud/login) workflow automation platform
  </Card>
</CardGroup>

<Tip>
  New to Notifier? [Sign up here](https://notifier.whatsable.app/)
</Tip>

## Set up your Notifier account

<Steps>
  <Step title="Configure your business information">
    First, let's set up your business profile in Notifier:

    1. Log in to your Notifier dashboard
    2. Navigate to **Business Information**
    3. Complete all required fields:
       * **Business Name**: Enter the name that will appear in messages sent to recipients
       * **Business Website or Social Media**: Add your website or social media URL
       * **Preferred Language**: Select the language for standard WhatsApp message elements
       * **Default Reply Text**: Create a template message that appears when recipients click "Reply"
       * **WhatsApp Number**: Add your business WhatsApp number where replies will be directed

    <Frame>
      <img alt="Configuring business information" />
    </Frame>

    <Note>
      After entering your WhatsApp number, Notifier will send a verification code to this number. Enter the code to verify ownership.
    </Note>

    Once saved, you'll see a preview of how your messages will appear to recipients. The actual message structure may vary slightly based on variables and attachments you include.
  </Step>

  <Step title="Get your API key">
    To connect Notifier with n8n, you'll need your API key:

    1. In your Notifier dashboard, go to **API Keys**
    2. Copy your unique API key
    3. Store it securely—you'll need it for the integration

    <Warning>
      Never share your API key publicly or commit it to version control systems.
    </Warning>
  </Step>
</Steps>

## Connect Notifier to n8n

Now that you have your Notifier account configured, let's connect it to n8n to automate your messaging workflows.

<Steps>
  <Step title="Set up your n8n workflow">
    1. Log in to your n8n account
    2. Create a new workflow/Zap by clicking **+ Create**
    3. Add a trigger node of your choice:
       * Popular triggers include Google Forms, Jotform, ClickUp, or a Schedule trigger
       * Connect and configure your trigger according to your use case

    <Accordion title="Whatsable trigger node (optional)">
      <Info>
        The Whatsable trigger node enables your workflow to respond automatically to incoming WhatsApp messages. This setup is optional but recommended for building reactive communication flows.
      </Info>

      <Steps>
        <Step title="Add Whatsable trigger node">
          Follow these steps to add the Whatsable trigger node to your workflow:

          1. Click the **+** button in your workflow canvas to add a new node
          2. Search for "Whatsable" in the node library search bar
          3. Select the node displaying the official Whatsable logo
          4. From the available trigger options, choose **On new Incoming message event**

          <Frame>
            <img alt="Whatsable node selection showing trigger options" />
          </Frame>

          <Tip>
            The trigger node will automatically listen for incoming messages and initiate your workflow when a new message is received.
          </Tip>
        </Step>

        <Step title="Configure authentication credentials">
          Set up your Whatsable API credentials to establish a secure connection:

          **Webhook URL Configuration:**

          1. In the Whatsable Trigger node parameters, locate the **Webhook URLs** section at the top
          2. Select **Production URL** and copy the generated URL by clicking on it
          3. Store this URL securely as you'll need it for the credential setup

          <Frame>
            <img alt="Production URL selection and copy interface" />
          </Frame>

          **Credential Creation:**

          1. In the **Credential to connect with** dropdown, click **+ Create new credential**
          2. Select **Whatsable Notifier API** as your connection method
          3. Enter your Notifier by Whatsable API key in the **API Key** field
          4. Paste the Production URL you copied earlier into the **Production URL** field
          5. Assign a descriptive name to your credential (e.g., "Whatsable Production")
          6. Click **Save** to securely store your credentials

          <Frame>
            <img alt="Whatsable credential configuration interface" />
          </Frame>

          <Note>
            Your API credentials are encrypted and stored securely. Never share your API key publicly or commit it to version control.
          </Note>
        </Step>

        <Step title="Test and activate workflow">
          Complete the setup by testing and activating your trigger:

          **Response Configuration:**

          1. In the **Respond** dropdown, select your preferred response timing:
             * **Immediately**: Responds as soon as the trigger fires
             * **When Last Node Finishes**: Waits for the entire workflow to complete before responding

          **Testing:**

          1. Click **Execute step** on the Whatsable node to run a test
          2. Verify the connection is working by checking for a success confirmation
          3. Review any error messages if the test fails and adjust your configuration accordingly

          <Check>
            Once activated, your workflow will automatically process incoming messages according to your configured logic.
          </Check>

          <Warning>
            Remember to test your workflow thoroughly before activating it in production to ensure it behaves as expected.
          </Warning>
        </Step>
      </Steps>
    </Accordion>
  </Step>

  <Step title="Add the Whatsable node">
    1. Click the **+** button to add a new node
    2. Search for "Whatsable" in the node library
    3. Select the node with the official Whatsable logo
    4. After selecting the Whatsable node, choose 'Send message via notifier' from the available actions menu

    <Frame>
      <img alt="Whatsable node selection" />
    </Frame>
  </Step>

  <Step title="Configure Notifier credential">
    1. In the Whatsable node **Parameters**, find the **Credential to connect with** dropdown
    2. Select **+ Create new credential**
    3. Enter your Notifier API key that you copied earlier
    4. Name your credential (e.g., "Notifier Production")
    5. Click **Save** to store your credential

    <Frame>
      <img alt="Configuring Notifier credential" />
    </Frame>
  </Step>

  <Step title="Configure your message">
    1. In **Resource** dropdown, select **Send Message**
    2. In the **Operation** dropdown, select **Send Message Via Notifier**
    3. Complete the required fields:

    <ResponseField name="Recipient" type="string">
      Enter the recipient's phone number (with country code) or use dynamic data from previous nodes
    </ResponseField>

    <ResponseField name="Message" type="string">
      Type your message text or use variables from previous nodes
    </ResponseField>

    <Expandable title="Optional Parameters">
      <ResponseField name="Attachment" type="file">
        Enter the URL of the file, image, or video you want to send with your message or use variables from previous nodes
      </ResponseField>

      <ResponseField name="File Name" type="string">
        Specify a custom filename for your attachment
      </ResponseField>
    </Expandable>
  </Step>

  <Step title="Test and activate your workflow">
    1. Click **Test Step** on the Notifier node to verify it's working correctly
    2. If the test is successful, you'll see a confirmation message
    3. Return to your workflow
    4. Click **Save** to save your entire workflow
    5. Toggle the **Active** switch in the top-right corner to activate your workflow

    <Check>
      Congratulations! Your Notifier and n8n integration is now complete! Your automated messaging workflow is now operational! Whenever your trigger conditions are met, n8n will automatically send WhatsApp messages through Notifier.
    </Check>
  </Step>
</Steps>

## Example workflows

Here are some powerful automation workflows you can build with Notifier and n8n:

<CardGroup>
  <Card title="Lead Nurturing" icon="user-plus">
    Send personalized WhatsApp messages to new leads who fill out your contact form
  </Card>

  <Card title="Order Confirmations" icon="box-check">
    Automatically notify customers when their order is placed, shipped, or delivered
  </Card>

  <Card title="Event Reminders" icon="calendar">
    Send timely WhatsApp reminders before scheduled events or appointments
  </Card>

  <Card title="Customer Feedback" icon="message-dots">
    Request feedback via WhatsApp after a customer interaction or purchase
  </Card>

  <Card title="Support Ticket Updates" icon="ticket">
    Keep customers informed about the status of their support requests
  </Card>
</CardGroup>

## Workflow Diagram

<Frame>
  ```mermaid theme={null}
  flowchart LR
    A[Trigger node] --> B[Data Transformation]
    B --> C[Notifier App]
    C --> D{Message Sent?}
    D -->|Yes| E[Success Path]
    D -->|No| F[Error Handling]
    E --> G[Additional Actions]
    F --> H[Retry Logic]
  ```
</Frame>

## Best practices

For optimal results when using Notifier with n8n:

<AccordionGroup>
  <Accordion title="Personalize your messages" icon="user-check">
    Use data from previous nodes in your workflow to create personalized, relevant messages for each recipient.
  </Accordion>

  <Accordion title="Keep messages concise" icon="text-size">
    Focus on a single call-to-action and keep your messages brief to maintain recipient engagement.
  </Accordion>

  <Accordion title="Test thoroughly" icon="flask">
    Always run complete tests of your workflow before deploying to production to catch any potential issues.
  </Accordion>

  <Accordion title="Monitor performance" icon="chart-line">
    Regularly check your Notifier dashboard to monitor delivery rates and optimize your messaging strategy.
  </Accordion>

  <Accordion title="Respect privacy" icon="shield-check">
    Always provide clear opt-out instructions and respect recipient preferences regarding messaging.
  </Accordion>
</AccordionGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Message not being sent?" icon="circle-exclamation">
    <Steps>
      <Step title="Check account status">
        Verify that your Notifier account is active and has available credits
      </Step>

      <Step title="Verify business information">
        Ensure your business information is complete and properly verified
      </Step>

      <Step title="Confirm API key">
        Double-check that your API key is entered correctly in n8n
      </Step>

      <Step title="Validate phone number">
        Confirm that the recipient's phone number is in the correct format (including country code)
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Formatting issues in messages?" icon="text-slash">
    <Steps>
      <Step title="Review template">
        Check your message template for any invalid characters or formatting issues
      </Step>

      <Step title="Variable formatting">
        Ensure variables from previous nodes are properly formatted
      </Step>

      <Step title="Message length">
        Verify your message doesn't exceed WhatsApp's length limitations
      </Step>
    </Steps>
  </Accordion>
</AccordionGroup>

## Need help?

Our support team is ready to assist you:

<CardGroup>
  <Card title="Email support" icon="envelope" href="mailto:team@whatsable.app">
    Contact [team@whatsable.app](mailto:team@whatsable.app)
  </Card>

  <Card title="Schedule a demo" icon="calendar" href="https://tidycal.com/axelmeta/notifier-systems-demo">
    Book a personalized walkthrough
  </Card>

  <Card title="Live chat" icon="message-dots" href="">
    Click the green chat button in the bottom right corner of the Notifier dashboard
  </Card>
</CardGroup>

<Info>
  For additional automation platform integrations (Make.com, Zapier, etc.), please contact our support team or check our integration documentation.
</Info>


# Zapier
Source: https://docs.whatsable.app/guides/notifier/zapier

Connect Notifier with Zapier to automate powerful WhatsApp messaging workflows

# Notifier Integration with Zapier

<Frame>
  <img />
</Frame>

<Info>
  Notifier enables you to send automated WhatsApp messages through your favorite workflow automation tools. This guide walks you through integrating Notifier with Zapier to create powerful messaging workflows
</Info>

## Prerequisites

Before getting started, make sure you have:

<CardGroup>
  <Card title="Notifier Account" icon="user">
    Active Notifier account with a subscription plan (Monthly or Pay-as-you-go)
  </Card>

  <Card title="Zapier Account" icon="user">
    Access to [Zapier](https://zapier.com/sign-up) workflow automation platform
  </Card>
</CardGroup>

<Tip>
  New to Notifier? [Sign up here](https://notifier.whatsable.app/)
</Tip>

## Set up your Notifier account

<Steps>
  <Step title="Configure your business information">
    First, let's set up your business profile in Notifier:

    1. Log in to your Notifier dashboard
    2. Navigate to **Business Information**
    3. Complete all required fields:
       * **Business Name**: Enter the name that will appear in messages sent to recipients
       * **Business Website or Social Media**: Add your website or social media URL
       * **Preferred Language**: Select the language for standard WhatsApp message elements
       * **Default Reply Text**: Create a template message that appears when recipients click "Reply"
       * **WhatsApp Number**: Add your business WhatsApp number where replies will be directed

    <Frame>
      <img alt="Configuring business information" />
    </Frame>

    <Note>
      After entering your WhatsApp number, Notifier will send a verification code to this number. Enter the code to verify ownership.
    </Note>

    Once saved, you'll see a preview of how your messages will appear to recipients. The actual message structure may vary slightly based on variables and attachments you include.
  </Step>

  <Step title="Get your API key">
    To connect Notifier with Zapier, you'll need your API key:

    1. In your Notifier dashboard, go to **API Keys**
    2. Copy your unique API key
    3. Store it securely—you'll need it for the integration

    <Warning>
      Never share your API key publicly or commit it to version control systems.
    </Warning>
  </Step>
</Steps>

## Connect Notifier to Zapier

Now that you have your Notifier account configured, let's connect it to Zapier to automate your messaging workflows.

<Steps>
  <Step title="Connect Notifier to Zapier">
    1. Log in to your Zapier account
    2. Navigate to Notifier dashboard and select **Connect to Zapier** in the side menu
    3. Click **Continue** in the connection guide popup
    4. Select Accept & Build a Zap on the invitation page

    <Check>
      You're now ready to create Zaps with the Notifier app
    </Check>
  </Step>

  <Step title="Set up your Zapier Zaps">
    1. Log in to your Zapier account
    2. Create a new workflow/Zap by clicking **+ Create** and select **Zaps**/**New Zap**
    3. Add a trigger step of your choice:
       * Popular triggers include Google Forms, Jotform, ClickUp, or a Schedule trigger
       * Connect and configure your trigger according to your use case

    <Frame>
      <img alt="Setting up Zapier Zaps" />
    </Frame>
  </Step>

  <Step title="Add the Notifier app">
    1. Select the next **Action** step or click the **+** button to add a new step
    2. Search for "Notifier by Whatsable" in the apps and tools library
    3. Select the app with the official Notifier logo

    <Frame>
      <img alt="Adding the Whatsable app" />
    </Frame>
  </Step>

  <Step title="Configure Notifier credentials">
    <Accordion title="Credential Setup">
      1. In the Notifier app Setup, select **Send WhatsApp Message** in the **Action event** dropdown
      2. Click **Sign In** in the **Account** field and you will be prompted to enter your API Key
      3. Enter your Notifier API key that you copied earlier
      4. Click **Yes, Continue to Notifier** to store your credential
      5. Next, click the **Continue** button in the Setup screen to proceed to the **Configure** section

      <Frame>
        <img alt="Configuring Notifier credentials" />
      </Frame>
    </Accordion>
  </Step>

  <Step title="Configure your message">
    Complete the required fields:

    <ResponseField name="Phone" type="string">
      Enter the recipient’s phone number (with country code) or use dynamic data from previous steps
    </ResponseField>

    <ResponseField name="Message Content" type="string">
      Type your message text or use variables from previous steps
    </ResponseField>

    <Expandable title="Optional Parameters">
      <ResponseField name="Attachment" type="file">
        Enter public URL of a file, image, or video to send with your message
      </ResponseField>

      <ResponseField name="File Name" type="string">
        Specify a custom filename for your attachment
      </ResponseField>

      <ResponseField name="Additional Parameters" type="object">
        Customize advanced options as needed
      </ResponseField>
    </Expandable>

    <br />

    <Frame>
      <img alt="Configuring message" />
    </Frame>
  </Step>

  <Step title="Test and activate your Zap">
    1. Click **Continue** and then click **Test step** in the **Test** to verify it's working correctly
    2. If the test is successful, you'll see a confirmation message
    3. Click **Publish** to save your entire Zap
    4. Toggle the **Active** switch in the top-left corner to activate your Zap
  </Step>
</Steps>

## Example use cases

<CardGroup>
  <Card title="Customer Onboarding" icon="user-plus">
    Send a welcome message when a new customer signs up
  </Card>

  <Card title="Order Notifications" icon="box-check">
    Update customers when their order status changes
  </Card>

  <Card title="Appointment Reminders" icon="calendar">
    Automatically send reminders before scheduled appointments
  </Card>

  <Card title="Lead Follow-up" icon="user-check">
    Send personalized messages to new leads from your form submissions
  </Card>

  <Card title="Support Ticket Updates" icon="ticket">
    Notify customers when their support ticket status changes
  </Card>
</CardGroup>

## Workflow Diagram

<Frame>
  ```mermaid theme={null}
  flowchart LR
    A[Trigger Step] --> B[Data Transformation]
    B --> C[Notifier App]
    C --> D{Message Sent?}
    D -->|Yes| E[Success Path]
    D -->|No| F[Error Handling]
    E --> G[Additional Actions]
    F --> H[Retry Logic]
  ```
</Frame>

## Best practices

For optimal results when using Notifier with Zapier:

<AccordionGroup>
  <Accordion title="Personalize your messages" icon="user-check">
    Use data from previous steps in your workflow to create personalized, relevant messages for each recipient.
  </Accordion>

  <Accordion title="Keep messages concise" icon="text-size">
    Focus on a single call-to-action and keep your messages brief to maintain recipient engagement.
  </Accordion>

  <Accordion title="Test thoroughly" icon="flask">
    Always run complete tests of your workflow before deploying to production to catch any potential issues.
  </Accordion>

  <Accordion title="Monitor performance" icon="chart-line">
    Regularly check your Notifier dashboard to monitor delivery rates and optimize your messaging strategy.
  </Accordion>

  <Accordion title="Respect privacy" icon="shield-check">
    Always provide clear opt-out instructions and respect recipient preferences regarding messaging.
  </Accordion>
</AccordionGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Message not being sent?" icon="circle-exclamation">
    <Steps>
      <Step title="Check account status">
        Verify that your Notifier account is active and has available credits
      </Step>

      <Step title="Verify business information">
        Ensure your business information is complete and properly verified
      </Step>

      <Step title="Confirm API key">
        Double-check that your API key is entered correctly in Zapier
      </Step>

      <Step title="Validate phone number">
        Confirm that the recipient's phone number is in the correct format (including country code)
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Formatting issues in messages?" icon="text-slash">
    <Steps>
      <Step title="Review template">
        Check your message template for any invalid characters or formatting issues
      </Step>

      <Step title="Variable formatting">
        Ensure variables from previous steps are properly formatted
      </Step>

      <Step title="Message length">
        Verify your message doesn't exceed WhatsApp's length limitations
      </Step>
    </Steps>
  </Accordion>
</AccordionGroup>

## Need help?

Our support team is ready to assist you:

<CardGroup>
  <Card title="Email support" icon="envelope" href="mailto:team@whatsable.app">
    Contact [team@whatsable.app](mailto:team@whatsable.app)
  </Card>

  <Card title="Schedule a demo" icon="calendar" href="https://tidycal.com/axelmeta/whatsapp-notifications-by-whatsable">
    Book a personalized walkthrough
  </Card>

  <Card title="Live chat" icon="message-dots" href="">
    Click the green chat button in the bottom right corner of the Notifier dashboard
  </Card>
</CardGroup>

<Info>
  For additional automation platform integrations (Make.com, n8n, etc.), please contact our support team or check our integration documentation.
</Info>


# Auth & environment
Source: https://docs.whatsable.app/guides/notifyer-system/agent-skills/auth-and-env

Environment variables, auth header modes (Console vs Chat vs Developer), and origin/CORS behavior used by Notifyer Agent Skills.

<Warning>
  Never commit tokens or API keys to Git. Treat `NOTIFYER_API_TOKEN` and the Developer API key as production secrets.
</Warning>

## Required environment variables

| Variable | Required | Default | Used for |
| - | -: | - | - |
| `NOTIFYER_API_BASE_URL` | **yes** | — | Base API host (must be HTTPS), e.g. `https://api.insightssystem.com` |
| `NOTIFYER_API_TOKEN` | **yes** (most scripts) | — | JWT returned by `setup-notifyer/scripts/login.js` |
| `NOTIFYER_CHAT_ORIGIN` | no | `https://chat.notifyer-systems.com` | Origin header for chat endpoints when overridden |

```bash theme={null}
export NOTIFYER_API_BASE_URL="https://api.insightssystem.com"
export NOTIFYER_API_TOKEN="eyJ..."
```

## Auth modes (critical)

Notifyer has **three auth modes** depending on the API surface. **The same JWT** is used for Console and Chat modes — only the header formatting differs.

| Mode | Header | Where it’s used |
| - | - | - |
| **Console** | `Authorization: Bearer <jwt>` | `setup-notifyer` and `automate-notifyer` (most endpoints) |
| **Chat** | `Authorization: <jwt>` (raw) | `chat-notifyer` and some web endpoints (labels/recipients/chat) |
| **Developer** | `Authorization: <api_key>` (raw) | Make/Zapier/n8n modules + direct developer send APIs |

<Tip>
  If you see HTTP 401 across many scripts, your JWT likely expired. Re-run `setup-notifyer/scripts/login.js` and re-export `NOTIFYER_API_TOKEN`.
</Tip>

## Origin headers & CORS behavior

Many Xano endpoints enforce allowed origins. The skills’ shared HTTP client automatically sends a correct `Origin` header per mode:

* Console-mode requests use `Origin: https://console.notifyer-systems.com`
* Chat-mode requests use `Origin: https://chat.notifyer-systems.com` (override with `NOTIFYER_CHAT_ORIGIN`)

This is important because “missing Origin” can cause silent or confusing auth failures on endpoints that validate it.

## Persisting environment variables

Add these exports to your shell profile:

<CodeGroup>
  ```bash theme={null}
  # ~/.zshrc
  export NOTIFYER_API_BASE_URL="https://api.insightssystem.com"
  export NOTIFYER_API_TOKEN="eyJ..."
  ```

  ```bash theme={null}
  # ~/.bashrc
  export NOTIFYER_API_BASE_URL="https://api.insightssystem.com"
  export NOTIFYER_API_TOKEN="eyJ..."
  ```
</CodeGroup>

## Security notes for CLI usage

<Warning>
  Passing secrets via CLI flags (like `--password`) can expose them via process lists (`ps aux`) on shared machines. Prefer using a password manager/secure terminal, and avoid logging stdout in shared CI environments.
</Warning>

## Related pages

* [`setup-notifyer`](/guides/notifyer-system/agent-skills/setup-notifyer) (login, doctor, API key)
* [`chat-notifyer`](/guides/notifyer-system/agent-skills/chat-notifyer) (chat origin and 24h window policy)
* [Security](/guides/notifyer-system/agent-skills/security)


# automate-notifyer
Source: https://docs.whatsable.app/guides/notifyer-system/agent-skills/automate-notifyer

Automation scripts for templates, AI bots, broadcasts, analytics, and webhooks — including outgoing WhatsApp Business app messages (coexistence).

<Tip>
  `automate-notifyer` builds on `setup-notifyer`. Always run `setup-notifyer/scripts/doctor.js` before sending templates, creating broadcasts, or configuring webhooks.
</Tip>

## What this skill covers

* **Templates**: create/list/get/delete; monitor Meta approval lifecycle
* **AI bots**: create/update/delete bots; set default bot
* **Broadcasts**: create/schedule campaigns using template + recipient CSV
* **Analytics & logs**: read rates, delivery rates, message logs
* **Webhooks**: create/update/delete **dev** and **IO** webhooks; optional HMAC signatures; `--incoming` and `--outgoing` so events include messages typed in the WhatsApp Business app

## Prerequisites

<Warning>
  Some features require a Pro or Agency plan (and an OpenAI key configured in Notifyer settings for bots). If you’re not sure, check with `setup-notifyer/scripts/get-user-plan.js`.
</Warning>

## Setup

```bash theme={null}
cd skills/automate-notifyer
export NOTIFYER_API_BASE_URL="https://api.insightssystem.com"
export NOTIFYER_API_TOKEN="eyJ..."
```

## Templates

List templates:

```bash theme={null}
node scripts/list-templates.js --pretty
node scripts/list-templates.js --status approved --pretty
```

Create a template (text with variables):

```bash theme={null}
node scripts/create-template.js \
  --name order_confirmation \
  --category MARKETING \
  --body "Hello {{1}}, your order #{{2}} is confirmed." \
  --variables '{"1":"John","2":"12345"}'
```

<Tip>
  `list-templates.js` auto-syncs `PENDING` template statuses from Meta on each call — you can re-run it to observe approval changes.
</Tip>

Delete a template:

```bash theme={null}
node scripts/delete-template.js --id 987654321 --confirm
```

## AI bots

```bash theme={null}
node scripts/list-bots.js --pretty
node scripts/create-bot.js --name "Support Bot" \
  --mission "Help users resolve support issues." \
  --knowledge-base "Return policy: 30 days. Shipping: 3-5 days." \
  --tone "Friendly" --delay 3 \
  --trigger-keywords "agent,human" --notification --default
node scripts/update-bot.js --id 12 --tone "Professional" --delay 5
node scripts/set-default-bot.js --id 12 --pretty
node scripts/delete-bot.js --id 12 --confirm --pretty
```

## Broadcasts

Create and schedule a broadcast (3-step flow):

```bash theme={null}
node scripts/create-broadcast.js \
  --name "January Sale" \
  --template-id 42 \
  --test-phone "+14155550123" \
  --recipients ./recipients.csv \
  --schedule "25/01/2025 14:00" \
  --delivery-mode smart \
  --delivery-size 4
```

<Warning>
  Phone numbers in the CSV must be **integers without `+`**. The schedule format is strictly `DD/MM/YYYY HH:mm` and is timezone-sensitive.
</Warning>

## Analytics & logs

```bash theme={null}
node scripts/get-message-analytics.js --days 30 --pretty
node scripts/get-message-analytics.js --from 2025-01-01 --to 2025-01-31 --pretty
node scripts/get-message-logs.js --filter broadcast --phone 14155550123 --pretty
```

## Webhooks

List webhooks:

```bash theme={null}
node scripts/list-webhooks.js --type dev --pretty
node scripts/list-webhooks.js --type io --pretty
```

Create a dev webhook (Make/Zapier/n8n style) that receives **incoming and outgoing** messages, including replies typed in the WhatsApp Business app:

```bash theme={null}
node scripts/create-webhook.js --type dev \
  --url "https://hook.eu2.make.com/abc" \
  --incoming --outgoing --signature
```

`--outgoing` is required if an automation must react to messages sent from the phone app, the Notifyer chat inbox, or other integrations. Payload fields: `incoming_message`, `send_by`, `was_message_by_human`. Full reference: [Message webhooks](/guides/notifyer-system/api/incoming-message).

## Incoming and outgoing WhatsApp messages

Notifyer delivers **both incoming and outgoing** messages to your webhook or automation trigger — including messages typed by hand in the **WhatsApp Business app** on your phone.

This is possible because Notifyer supports [Meta WhatsApp Coexistence](/guides/notifyer-system/embedding-process#whatsapp-coexistence). You keep using WhatsApp Business on your phone; those hand-typed replies still reach an external webhook and can start an automation. They are not limited to the Notifyer web inbox.

<Frame>
  <iframe title="Trigger n8n workflows with WhatsApp messages" />
</Frame>

The payload is the same whether you use [n8n](/guides/notifyer-system/n8n-overview), [Make](/guides/notifyer-system/make-overview), [Zapier](/guides/notifyer-system/zapier-overview), or a [custom webhook](/guides/notifyer-system/api/incoming-message). [Watch the walkthrough on YouTube](https://www.youtube.com/watch?v=UfW-KwS4gBI).

### Direction, sending system, and team member

Use these three fields to tell *what happened* and *who sent it*:

<ResponseField name="incoming_message" type="boolean">
  `true` when a contact sent a message **to** your business. `false` when your business sent a message **to** the contact (outgoing). Filter on this field to run logic only for one direction.
</ResponseField>

<ResponseField name="send_by" type="string">
  Which system or person sent an **outgoing** message:

  | `send_by` value | Meaning |
  | - | - |
  | `WhatsApp App` | Typed by hand in the WhatsApp Business app on a phone |
  | A team member's name (for example `Axel Meta`) | Sent from the Notifyer chat inbox by that logged-in user |
  | An automation or app name (Make, Zapier, n8n, API, bot) | Sent by that integration or bot |

  Empty or omitted on incoming messages.
</ResponseField>

<ResponseField name="was_message_by_human" type="boolean">
  `true` when a person sent the message (WhatsApp Business app or Notifyer chat inbox). `false` when a bot or automation sent it. Combine with `send_by` to see both *whether* a human sent it and *which teammate or system* did.
</ResponseField>

### Example payload: message typed on the phone

This is the JSON Notifyer POSTs when someone types a reply in the WhatsApp Business app. `incoming_message` is `false`, `send_by` is `"WhatsApp App"`, and `was_message_by_human` is `true`.

```json theme={null}
{
  "last_messages": "[{\"type\":\"bot\",\"content\":\"Hello n8n\",\"timestamp\":\"2026-08-15T12:24:47.000Z\",\"content_type\":\"text\"},{\"type\":\"user\",\"content\":\"hi\",\"timestamp\":\"2026-08-12T12:27:42.746Z\",\"content_type\":\"text\"}]",
  "conversation_paragraph": "Bot (12:24:47 PM): Hello n8n ; User (12:27:42 PM): hi",
  "phone_number": 14155552671,
  "recipient_name": "Alex Martinez",
  "user_id": "158c59e1-ea85-4d0b-b70c-65328ba67a8e",
  "last_message_of_user": "hi",
  "last_message_of_bot": "Hello n8n",
  "message_type": "text",
  "user_last_message_time": 1786722580,
  "bot_last_message_time": 1786797014,
  "attachment_url": null,
  "note": "email: alex\nName: Alex",
  "note_automation": "email: alex\nName: Alex",
  "labels": "n8n, webhook-test",
  "incoming_message": false,
  "send_by": "WhatsApp App",
  "was_message_by_human": true
}
```

<Note>
  `last_message_of_bot` is the last message **your business** sent — whether a human typed it in the WhatsApp Business app or the Notifyer inbox, or a bot/automation sent it. `last_messages` is a JSON **string** of the last \~20 messages (parse it before iterating). `phone_number` may arrive as a number rather than a string.
</Note>

When the same person sends from the Notifyer chat inbox instead of the phone app, the payload is identical except:

```json theme={null}
{
  "incoming_message": false,
  "send_by": "Axel Meta",
  "was_message_by_human": true
}
```

Create an IO webhook (bidirectional pipeline style):

```bash theme={null}
node scripts/create-webhook.js --type io \
  --url "https://myapp.com/webhook" \
  --signature
```

Update/delete:

```bash theme={null}
node scripts/update-webhook.js --type dev --id 5 --status false
node scripts/delete-webhook.js --type dev --id 5 --confirm
```

<Tip>
  Dev webhook `id` is an integer. IO webhook `id` is a **text UUID** — treat it as a string.
</Tip>

## Next

* Operate conversations: [`chat-notifyer`](/guides/notifyer-system/agent-skills/chat-notifyer)
* See end-to-end automation flows: [Use cases](/guides/notifyer-system/agent-skills/use-cases)


# chat-notifyer
Source: https://docs.whatsable.app/guides/notifyer-system/agent-skills/chat-notifyer

Live chat operations: recipients, messaging (text/template/attachments), labels, handoff, scheduling, notes, and conversation history.

<Tip>
  Use `chat-notifyer` when you want an agent to operate active WhatsApp conversations (similar to `chat.notifyer-systems.com`) via scripts.
</Tip>

## Prerequisites

* You have a valid JWT in `NOTIFYER_API_TOKEN` (from `setup-notifyer/scripts/login.js`)
* WhatsApp connection is active (verify with `setup-notifyer/scripts/get-connection-status.js`)

## Auth mode difference (don’t miss this)

<Warning>
  Chat endpoints use **raw JWT** auth: `Authorization: <jwt>` (no `Bearer` prefix). Console endpoints use `Authorization: Bearer <jwt>`.
</Warning>

The shared client handles this automatically. See [Auth & environment](/guides/notifyer-system/agent-skills/auth-and-env).

## The 24-hour window rule (critical)

WhatsApp allows **free text** and **attachments** only within **24 hours** of a user’s last inbound message.

| Window | Allowed |
| - | - |
| Open | Text ✓, Template ✓, Attachment ✓ |
| Closed | Template only ✓ |

Check window state:

```bash theme={null}
node scripts/get-recipient.js --phone 14155550123 --pretty
```

`send-text.js` enforces this automatically and will refuse if the window is closed.

## Common workflows

### List/search recipients

```bash theme={null}
node scripts/list-recipients.js --pretty
node scripts/list-recipients.js --search "John" --pretty
node scripts/list-recipients.js --status unread --pretty
```

### Filter recipients by label

```bash theme={null}
node scripts/filter-recipients-by-label.js --labels "Support" --status unread --pretty
```

### Send a text message

```bash theme={null}
node scripts/send-text.js --phone 14155550123 --text "Hello! How can I help?"
```

### Send a template message (works any time)

```bash theme={null}
node scripts/send-template.js --list
node scripts/send-template.js --phone 14155550123 --name order_confirm \
  --variables '{"body1":"John","body2":"#12345"}'
node scripts/send-template.js --phone 14155550123 --name order_confirm --dry-run
```

### Send an attachment

```bash theme={null}
node scripts/send-attachment.js --phone 14155550123 --file ./invoice.pdf --pretty
node scripts/send-attachment.js --phone 14155550123 --file ./photo.jpg --caption "Your order photo"
```

### Schedule a send

```bash theme={null}
node scripts/send-template.js --phone 14155550123 --name order_confirm --schedule "25/01/2025 14:00"
node scripts/list-scheduled.js --pretty
node scripts/delete-scheduled.js --id 7 --confirm
```

### Labels (assign/remove)

```bash theme={null}
node scripts/assign-label.js --phone 14155550123 --label "Support" --pretty
node scripts/remove-label.js --phone 14155550123 --label "Support" --pretty
```

Labels must exist first (create via `setup-notifyer/create-label.js`).

### AI ↔ Human handoff

```bash theme={null}
node scripts/set-handoff.js --phone 14155550123 --mode human --pretty
node scripts/set-handoff.js --phone 14155550123 --mode bot --pretty
```

Assign a specific bot:

```bash theme={null}
node scripts/list-bots.js --pretty
node scripts/assign-bot.js --phone 14155550123 --bot-id 5 --pretty
```

### Conversation + notes

```bash theme={null}
node scripts/get-conversation.js --phone 14155550123 --pretty
node scripts/get-conversation-log.js --phone 14155550123 --pretty
node scripts/get-notes.js --phone 14155550123 --pretty
node scripts/add-note.js --phone 14155550123 --append "Requested callback on 15 Feb"
```

<Tip>
  `get-conversation.js` returns the **full** thread (sent + received). `get-conversation-log.js` is **outbound-only** delivery history.
</Tip>

## Next

* End-to-end operational playbooks: [Use cases](/guides/notifyer-system/agent-skills/use-cases)
* If you hit send failures: [Troubleshooting](/guides/notifyer-system/agent-skills/troubleshooting)


# Agent Skills (Notifyer)
Source: https://docs.whatsable.app/guides/notifyer-system/agent-skills/overview

Notifyer Agent Skills for setup, automation, chat, and webhooks. Coexistence is supported — you do not delete the WhatsApp Business app. Webhooks include outgoing messages with send_by and was_message_by_human.

<Tip>
  Agent Skills let AI coding agents (Cursor, OpenClaw, Claude Code, Copilot, etc.) authenticate into Notifyer and operate your workspace programmatically — using the same backend API surface as the Notifyer Console and Chat apps.
</Tip>

<Info>
  **Meta WhatsApp Coexistence is supported on Notifyer System.** You do **not** need to delete the WhatsApp Business app or stop using the number on your phone. After Embedded Signup, the same number works in the WhatsApp Business app, the Notifyer chat inbox, and automations (Make, Zapier, n8n, API, and webhooks) at the same time.
</Info>

## What are Agent Skills?

**Notifyer Agent Skills** are a set of **Node.js scripts + a `SKILL.md` instruction file** that teach compatible AI agents how to:

* Authenticate into a Notifyer workspace
* Validate prerequisites (connection, plan, token health)
* Configure workspace infrastructure (labels, team, API key)
* Manage automation primitives (templates, AI bots, broadcasts, webhooks, analytics)
* Operate live chat workflows (recipients, messages, handoff, notes, scheduling)

They follow the open [AgentSkills standard](https://agentskills.io/specification), which allows many agents to discover and load skills on demand.

## How this fits inside Notifyer System docs

Notifyer System can be operated via:

<Tabs>
  <Tab title="Developer API (integrations)">
    Use API keys for Make/Zapier/n8n or your backend services. This is the best choice when you’re building **event-driven automations** and do not need to manage workspace configuration.
  </Tab>

  <Tab title="Agent Skills (operations)">
    Use Agent Skills when you want an AI coding agent to **set up**, **configure**, or **operate** a Notifyer workspace end-to-end: onboarding, template lifecycle, broadcasts, webhooks, and live chat operations.
  </Tab>

  <Tab title="Console/Chat UI (manual)">
    Use the web apps when you’re doing the initial WhatsApp onboarding, billing changes, or manual team operations.
  </Tab>
</Tabs>

## Skill set overview (3 phases)

The skills are designed as a progressive sequence.

| Phase | Skill | Primary purpose |
| - | - | - |
| 1 | `setup-notifyer` | Authentication, workspace identity, WhatsApp connection status, plans, team/roles, labels, Developer API key |
| 2 | `automate-notifyer` | Templates, AI bots, broadcasts, analytics/logs, webhooks |
| 3 | `chat-notifyer` | Recipients, messaging, labels, AI/human handoff, scheduled sends, notes, conversation history |

## What you can automate (examples)

* **Workspace onboarding**: create labels, invite members, verify connection and plan, fetch the Developer API key.
* **Template lifecycle**: create templates, monitor Meta approval status, use approved templates in broadcasts.
* **Customer support ops**: fetch conversation context, take over from bot, respond, label, add notes, return to bot.
* **Webhook configuration**: create dev and IO webhooks with HMAC signature; enable `--incoming` and `--outgoing` so events include messages typed in the WhatsApp Business app. Payload fields: `incoming_message`, `send_by` (system or teammate), `was_message_by_human`. See [Message webhooks](/guides/notifyer-system/api/incoming-message).

For end-to-end workflows, see [Use cases](/guides/notifyer-system/agent-skills/use-cases).

## Important constraints (read before you automate)

<Warning>
  Some actions are intentionally not scriptable:

  * First-time WhatsApp connection (embedded signup / QR scan) is **browser-only**. You do **not** need to delete the WhatsApp Business app — [coexistence](/guides/notifyer-system/embedding-process#whatsapp-coexistence) is supported.
  * Billing changes and Stripe flows are **browser-only**.
  * Meta template approval timing is **not controllable** via API.
</Warning>

## Next steps

* Start with [Quickstart](/guides/notifyer-system/agent-skills/quickstart)
* Configure [Auth & environment](/guides/notifyer-system/agent-skills/auth-and-env)
* Dive into each skill:
  * [`setup-notifyer`](/guides/notifyer-system/agent-skills/setup-notifyer)
  * [`automate-notifyer`](/guides/notifyer-system/agent-skills/automate-notifyer)
  * [`chat-notifyer`](/guides/notifyer-system/agent-skills/chat-notifyer)

<CardGroup>
  <Card title="Whatsable/whatsapp-business-agent-skills" icon="github" href="https://github.com/Whatsable/whatsapp-business-agent-skills">
    Official repository for Notifyer Agent Skills, including scripts, reference material, and `SKILL.md` entrypoints.
  </Card>
</CardGroup>


# Using with Base44
Source: https://docs.whatsable.app/guides/notifyer-system/agent-skills/platforms/base44

Install Notifyer Agent Skills so your AI coding assistant can build and operate Notifyer integrations inside Base44 apps.

<Tip>
  Base44 follows the open [AgentSkills specification](https://agentskills.io/specification). Notifyer Agent Skills can be installed globally so any AI coding assistant you use with Base44 — Claude, Cursor, Copilot, or others — knows how to call the Notifyer API.
</Tip>

## How skills work in Base44

Base44 uses Agent Skills to give external AI coding tools reusable instructions for platform-specific tasks. When you install Notifyer skills globally, your AI assistant gains:

* Knowledge of all Notifyer API endpoints, auth modes, and CORS rules
* Ready-to-run Node.js scripts for every Notifyer operation
* Reference documentation on templates, broadcasts, recipients, webhooks, and chat

The skills are loaded from `~/.agents/skills/` (global) or `.agents/skills/` (project-level) and are used by the AI when you ask it to add Notifyer functionality to a Base44 app or backend function.

***

## Install the skills

<Tabs>
  <Tab title="Global install (recommended)">
    Makes the skills available across all your Base44 projects. Use `--all` to install all three skills at once without an interactive prompt:

    ```bash theme={null}
    npx skills add whatsable/whatsapp-business-agent-skills --all -g
    ```

    This installs `setup-notifyer`, `automate-notifyer`, and `chat-notifyer` together.

    To install interactively (choose which skills to include):

    ```bash theme={null}
    npx skills add whatsable/whatsapp-business-agent-skills -g
    ```

    To install a single skill only:

    ```bash theme={null}
    npx skills add whatsable/whatsapp-business-agent-skills --skill chat-notifyer -g
    ```
  </Tab>

  <Tab title="Project-level install">
    Installs only into the current project directory:

    ```bash theme={null}
    npx skills add whatsable/whatsapp-business-agent-skills --all
    ```
  </Tab>
</Tabs>

<Tip>
  Base44 skills themselves are installed with `npx skills add base44/skills -g`. Notifyer skills are a separate add-on — install both if you're building a Base44 app that sends WhatsApp messages via Notifyer.
</Tip>

***

## Set up environment variables

The Notifyer scripts need these variables:

| Variable | Required | Description |
| - | - | - |
| `NOTIFYER_API_BASE_URL` | **yes** | Always `https://api.insightssystem.com`. Must start with `https://` — all scripts enforce this at startup. |
| `NOTIFYER_API_TOKEN` | **yes** | JWT token obtained via `setup-notifyer/scripts/login.js` |
| `NOTIFYER_CHAT_ORIGIN` | no | CORS Origin override for Phase 3 chat endpoints. Defaults to `https://chat.notifyer-systems.com`. |

```bash theme={null}
export NOTIFYER_API_BASE_URL="https://api.insightssystem.com"
export NOTIFYER_API_TOKEN="eyJ..."   # obtained via setup-notifyer/scripts/login.js
```

For Base44 backend functions that call the Notifyer API directly, store these as **project secrets** using the Base44 CLI:

```bash theme={null}
base44 secrets set NOTIFYER_API_BASE_URL=https://api.insightssystem.com
base44 secrets set NOTIFYER_API_TOKEN=eyJ...
```

Inside your backend function code, access them with `Deno.env.get("NOTIFYER_API_TOKEN")`.

<Warning>
  Never hardcode `NOTIFYER_API_TOKEN` in your Base44 app source. Use `base44 secrets set` to store it securely — it will be available as an environment variable in your deployed backend functions.
</Warning>

***

## Two ways to use Notifyer in a Base44 app

### 1. AI-assisted integration (skills-guided)

Tell your AI coding assistant to add Notifyer functionality to a Base44 backend function. With the skills installed, the AI already knows the correct API endpoints, auth headers, and payload shapes:

```
Add a Base44 backend function called sendWhatsAppTemplate that accepts a phone number
and template name, authenticates with the Notifyer API using NOTIFYER_API_TOKEN,
and sends the matching approved template.
```

```
Create a Base44 backend function that checks if a recipient's 24-hour WhatsApp
messaging window is open before sending a text message via Notifyer.
```

The AI will reference the skill's reference docs (`references/messaging-reference.md`, `references/recipients-reference.md`, etc.) to produce accurate code.

### 2. Calling the Notifyer API directly from a Base44 backend function

Base44 backend functions run on **Deno** — not Node.js. Call the Notifyer REST API directly using the built-in `fetch()`. The Notifyer scripts (which require Node.js 18+) cannot be executed from within a Deno backend function.

The example below sends a WhatsApp template message using the Notifyer Chat API (`POST /api:bVXsw_FD/web/send/template`). Template messages work at any time — no 24-hour window required. Get the `templateId` from `automate-notifyer/scripts/list-templates.js`.

```typescript theme={null}
// Inside a Base44 backend function (Deno)
Deno.serve(async (req) => {
  try {
    const { phone, templateId, variables } = await req.json();

    const token = Deno.env.get("NOTIFYER_API_TOKEN");
    const baseUrl = Deno.env.get("NOTIFYER_API_BASE_URL");

    const res = await fetch(`${baseUrl}/api:bVXsw_FD/web/send/template`, {
      method: "POST",
      headers: {
        "Authorization": token,          // Chat auth — raw JWT, no Bearer prefix
        "Origin": "https://chat.notifyer-systems.com",
        "Content-Type": "application/json",
      },
      body: JSON.stringify({
        template: templateId,            // Template ID string from list-templates.js
        variables: variables ?? {},      // e.g. { "body1": "John", "body2": "#12345" }
        current_recipient: {
          phone_number: parseInt(String(phone).replace(/^\+/, ""), 10),
        },
        scheduled_time: 0,              // 0 = send immediately
      }),
    });

    const result = await res.json();

    // Notifyer (Xano) can return HTTP 200 with success: false on Meta rejections
    if (!res.ok || result.success === false) {
      return Response.json(
        { ok: false, error: result },
        { status: res.ok ? 400 : res.status }
      );
    }

    return Response.json({ ok: true, result });
  } catch (error) {
    return Response.json({ ok: false, error: error.message }, { status: 500 });
  }
});
```

<Warning>
  Base44 backend functions use the Deno runtime. Do not import Node.js-specific modules like `child_process`. Use `fetch()` to call the Notifyer REST API directly, and use `Deno.env.get()` to read secrets.
</Warning>

***

## Example AI prompts for Base44 projects

With Notifyer skills installed, give your AI assistant these kinds of instructions:

### Send WhatsApp messages from a Base44 app

```
Build a Base44 backend function called notifyCustomer.
It should accept { phone, templateName, variables } and send a WhatsApp template
message via the Notifyer API. Use NOTIFYER_API_BASE_URL and NOTIFYER_API_TOKEN
from environment variables. Handle errors and return { ok, message_id } or { ok: false, error }.
```

### Trigger a broadcast from a Base44 automation

```
Add a Base44 automation that runs daily at 9am, fetches all customers from the
Customers entity with status = "trial_expiring", and triggers a Notifyer broadcast
using the trial_reminder template for each one.
```

### Webhook receiver in Base44

```
Create a Base44 backend function to receive incoming Notifyer IO webhook events.
Validate the HMAC signature using NOTIFYER_WEBHOOK_SECRET.
When a new inbound message arrives, create or update a record in the Conversations entity.
```

### Chat handoff from a Base44 agent

```
When a user sends the message "talk to a human" to our Base44 AI agent,
perform a human handover for that contact's WhatsApp conversation in Notifyer.
Use the assign-label workflow: first get the bot's handoff_label from list-bots.js,
then assign that label to the recipient — this automatically stops the AI bot and
routes the conversation to the human agent queue.
```

<Note>
  The correct handover method is **always label-based**: assign the bot's configured `handoff_label` to the recipient. Notifyer automatically sets `is_ai_assistant = false` when the handoff label is detected. Do not use a direct PATCH to flip `is_ai_assistant` — it stops the bot but does not route to the human label queue.
</Note>

***

## API reference for Base44 backend functions

When building backend functions that call Notifyer directly, these are the key details:

| | Console API | Chat API |
| - | - | - |
| **Base URL** | `NOTIFYER_API_BASE_URL` | `NOTIFYER_API_BASE_URL` |
| **Auth header** | `Authorization: Bearer <jwt>` | `Authorization: <jwt>` (no Bearer) |
| **Origin** | `https://console.notifyer-systems.com` | `https://chat.notifyer-systems.com` |
| **Used for** | Templates, bots, broadcasts, webhooks | Recipients, messaging, labels, handoff |

There is also a **Developer API key** mode (`Authorization: <api_key>` — no Bearer prefix) used by external tools such as Make, Zapier, and n8n. Retrieve the key with `setup-notifyer/scripts/get-api-key.js`. This is a separate long-lived credential, distinct from the JWT token.

For complete endpoint reference, see the skills' `references/` directory after install:

* `~/.agents/skills/automate-notifyer/references/`
* `~/.agents/skills/chat-notifyer/references/`

***

## Keeping skills up to date

```bash theme={null}
npx skills add whatsable/whatsapp-business-agent-skills --all -g
```

Re-running the install command pulls the latest version from the repository.

***

## Related pages

* [Quickstart](/guides/notifyer-system/agent-skills/quickstart)
* [Auth & environment](/guides/notifyer-system/agent-skills/auth-and-env)
* [Use cases](/guides/notifyer-system/agent-skills/use-cases)
* [Base44 Skills docs](https://docs.base44.com/developers/backend/overview/skills)
* [Base44 Backend Functions](https://docs.base44.com/developers/backend/resources/backend-functions/overview)
* [Base44 Secrets (`secrets set`)](https://docs.base44.com/developers/references/cli/commands/secrets-set)


# Using with Cursor
Source: https://docs.whatsable.app/guides/notifyer-system/agent-skills/platforms/cursor

Install Notifyer Agent Skills into Cursor and have its Agent operate your Notifyer workspace from inside your IDE.

<Tip>
  Cursor has **native support** for the AgentSkills standard. Skills installed via `npx skills add` are automatically discovered by Cursor Agent — no manual configuration needed.
</Tip>

## How it works in Cursor

Cursor Agent loads skills from these directories and presents them as available capabilities:

| Location | Scope |
| - | - |
| `.cursor/skills/<skill-name>/` | Current project only |
| `.agents/skills/<skill-name>/` | Current project only |
| `~/.cursor/skills/<skill-name>/` | All projects (global) |
| `~/.agents/skills/<skill-name>/` | All projects (global) |

When a skill is installed, Agent reads its `SKILL.md` file and automatically decides when to apply it based on what you ask. You can also invoke any skill explicitly by typing `/skill-name` in the Agent chat.

Skills are visible in **Cursor Settings → Rules → Agent Decides**.

***

## Install the skills

<Tabs>
  <Tab title="Global install (recommended)">
    Installs the skills for all your projects. Run once:

    ```bash theme={null}
    npx skills add whatsable/whatsapp-business-agent-skills -g
    ```

    This puts all 3 skills under `~/.agents/skills/`:

    * `~/.agents/skills/setup-notifyer/`
    * `~/.agents/skills/automate-notifyer/`
    * `~/.agents/skills/chat-notifyer/`
  </Tab>

  <Tab title="Project-level install">
    Installs only into the current project's `.agents/skills/` directory:

    ```bash theme={null}
    npx skills add whatsable/whatsapp-business-agent-skills
    ```

    When prompted, select the skills you want, or select **All 3 skills** to install everything at once.
  </Tab>

  <Tab title="Install a single skill">
    ```bash theme={null}
    npx skills add whatsable/whatsapp-business-agent-skills --skill setup-notifyer
    npx skills add whatsable/whatsapp-business-agent-skills --skill automate-notifyer
    npx skills add whatsable/whatsapp-business-agent-skills --skill chat-notifyer
    ```
  </Tab>
</Tabs>

<Warning>
  The scripts in these skills are **Node.js CLI tools** that run in your terminal, not inside Cursor's chat UI. Cursor Agent reads the skill instructions and executes scripts using its terminal tool when needed.
</Warning>

***

## Set up environment variables

The scripts need two variables before Agent can use them:

```bash theme={null}
export NOTIFYER_API_BASE_URL="https://api.insightssystem.com"
export NOTIFYER_API_TOKEN="eyJ..."   # obtained via setup-notifyer/scripts/login.js
```

Add these to your shell profile (`~/.zshrc` or `~/.bashrc`) so they're always available when Cursor's terminal runs scripts. Alternatively, add a `.env` file to your project — Cursor Agent can read it if you reference it in your prompt.

<Warning>
  Never commit `NOTIFYER_API_TOKEN` to Git. The `.gitignore` in the agent-skills repo already excludes `.env` and `.env.*` files.
</Warning>

For full environment variable reference, see [Auth & environment](/guides/notifyer-system/agent-skills/auth-and-env).

***

## Verify discovery

After installing, confirm Cursor can see the skills:

1. Open **Cursor Settings** → **Rules**
2. Look for `setup-notifyer`, `automate-notifyer`, and `chat-notifyer` in the **Agent Decides** section

Or run in Cursor Agent chat:

```
/setup-notifyer
```

Agent will display the skill instructions and confirm it's loaded.

***

## Example Agent prompts

Once installed, use natural language in Cursor Agent chat. Agent will identify the relevant skill and execute the appropriate scripts.

### Workspace setup

```
Log in to Notifyer with email=me@company.com and run a full health check.
Tell me if the WhatsApp connection is active and what plan we're on.
```

```
Create three labels: Sales, Support, and VIP.
For each one, set up relevant keywords (e.g. "pricing, quote" for Sales).
```

### Template management

```
List all our approved WhatsApp templates and show me which ones have variables.
```

```
Create a new template called order_shipped in the UTILITY category.
Body: "Hi {{1}}, your order {{2}} has shipped and will arrive by {{3}}."
```

### Live chat operations

```
Find all unread conversations labeled VIP and show me the full context for each one.
```

```
Check if the 24-hour messaging window is open for +14155550123, then send them
"Hi! Just following up on your recent enquiry." if it is.
```

```
Assign the Support label to +14155550123, take over from the bot, and add a note:
"Customer escalated — awaiting approval from billing team."
```

### Broadcast campaigns

```
Create a broadcast called Feb Promo using template ID 42.
Test it on +14155550123 first, then schedule it for 01/02/2026 at 10:00.
```

***

## Manually invoking a skill

If Agent doesn't pick up a skill automatically, invoke it with the `/` command:

```
/setup-notifyer Run doctor.js and tell me what's wrong.
```

```
/chat-notifyer Get the last 20 messages from the conversation with +14155550123.
```

```
/automate-notifyer List all webhooks and show me which ones have signatures enabled.
```

***

## How Agent runs the scripts

When you give Agent a task, it:

1. Reads the relevant `SKILL.md` to understand available scripts and their flags
2. Opens a terminal in the skill's directory (`skills/setup-notifyer/`, etc.)
3. Runs the script with the correct flags
4. Parses the JSON output (`ok`/`err` structure) and summarises the result

All scripts output structured JSON, which Agent can read and act on — for example, it can check if `isConnected: false` and automatically suggest running `refresh-connection.js`.

***

## Keeping skills up to date

```bash theme={null}
# Re-run the install command to pull the latest version
npx skills add whatsable/whatsapp-business-agent-skills -g
```

***

## Related pages

* [Quickstart](/guides/notifyer-system/agent-skills/quickstart)
* [Auth & environment](/guides/notifyer-system/agent-skills/auth-and-env)
* [Use cases](/guides/notifyer-system/agent-skills/use-cases)
* [Cursor Agent Skills docs](https://cursor.com/docs/skills)


# Using with Lovable
Source: https://docs.whatsable.app/guides/notifyer-system/agent-skills/platforms/lovable

Teach Lovable's AI agent how to build Notifyer WhatsApp integrations. Coexistence is supported; webhooks include outgoing messages with send_by and was_message_by_human.

<Info>
  **Meta WhatsApp Coexistence is supported on Notifyer System.** You do **not** need to delete the WhatsApp Business app or stop using the number on your phone. After Embedded Signup, the same number works in the WhatsApp Business app, the Notifyer chat inbox, and automations (Make, Zapier, n8n, API, and webhooks) at the same time.
</Info>

<Note>
  Lovable's web agent does not read skill files from `.agents/skills/` or `.cursor/skills/` — it only reads **Project knowledge**, **Workspace knowledge**, `AGENTS.md`, and `CLAUDE.md` from your GitHub repo. The `npx skills add` CLI has no direct effect on what Lovable sees.

  However, Lovable projects are GitHub-backed. If you also work on the same project locally in **Cursor** (a common hybrid workflow), you should install the skills there too — see the [Cursor guide](/guides/notifyer-system/agent-skills/platforms/cursor).
</Note>

## How Lovable reads context

Lovable's agent considers several context sources when generating code:

| Source | How to set it | Scope |
| - | - | - |
| **Project knowledge** | Project settings → Knowledge | One project |
| **Workspace knowledge** | Settings → Knowledge | All projects in workspace |
| **`AGENTS.md` / `CLAUDE.md`** | Root of the GitHub repo linked to the project | Always loaded regardless of session length |
| **Integration knowledge** | Via connected services (e.g. Supabase) | Per integration |

<Tip>
  `AGENTS.md` and `CLAUDE.md` at the repo root are always read by Lovable, even in very long sessions where project or workspace knowledge may not always be followed consistently. Use them for rules that must never be lost.
</Tip>

For Notifyer integrations, the most reliable approach is to put the critical API context in **Project knowledge** and keep the `AGENTS.md` file for structural rules that must persist across long sessions.

***

## Option 1 — Project Knowledge (recommended)

Add the following to your project's **Project settings → Knowledge**. This tells Lovable's agent exactly how to call the Notifyer API when building your app.

```text theme={null}
Notifyer WhatsApp API integration

Base URL: stored in env var NOTIFYER_API_BASE_URL (e.g. https://api.insightssystem.com)
Auth token: stored in env var NOTIFYER_API_TOKEN (JWT from login)

Auth headers:
- Console API (templates, bots, broadcasts, webhooks):
    Authorization: Bearer <NOTIFYER_API_TOKEN>
    Origin: https://console.notifyer-systems.com
- Chat API (recipients, messaging, labels, handoff):
    Authorization: <NOTIFYER_API_TOKEN>  (no Bearer prefix)
    Origin: https://chat.notifyer-systems.com

Key API groups:
- /api:AFRA_QCy/ — templates
- /api:ox_LN9zX/ — bots
- /api:Mk_r6mq0/ — broadcasts
- /api:bVXsw_FD/ — chat recipients and messaging
- /api:qh9OQ3OW/ — message logs and analytics
- /api:0hqyGRIz/ — webhooks (enable incoming AND outgoing)

Critical rules:
- Never hardcode NOTIFYER_API_TOKEN in source code — always use env vars.
- Text and attachment messages require the recipient to have messaged in the last 24 hours.
  If window is closed, use a template message instead.
- global_label is a string[] of label names, not IDs.
- PATCH /web/recipient/:id requires the full recipient body (fetch first, then patch).
- Schedule timestamp is ms since epoch; 0 means immediate send.
- NOTIFYER_API_BASE_URL must be HTTPS — reject any http:// value.
- Meta WhatsApp Coexistence is supported. Do NOT tell users to delete the WhatsApp Business app.
- Webhooks fire for incoming AND outgoing messages (including hand-typed WhatsApp Business app replies).
  Payload fields: incoming_message (boolean), send_by ("WhatsApp App" | teammate name | automation name),
  was_message_by_human (boolean). last_messages is often a JSON string — parse it.
- Full webhook reference: https://docs.whatsable.app/guides/notifyer-system/api/incoming-message
- Coexistence / embedding: https://docs.whatsable.app/guides/notifyer-system/embedding-process

Reference:
- Full API documentation: https://github.com/Whatsable/whatsapp-business-agent-skills
- Script reference: skills/chat-notifyer/scripts/ and skills/automate-notifyer/scripts/
```

<Tip>
  Project Knowledge supports up to **10,000 characters**. The block above is intentionally concise. Expand it with specific endpoint shapes or payload examples if your project needs precise API call generation.
</Tip>

***

## Option 2 — AGENTS.md in your GitHub repo

For rules that must survive long Lovable chat sessions, add an `AGENTS.md` file to the root of the GitHub repository linked to your Lovable project. Lovable always reads root-level `AGENTS.md` files regardless of session length.

Create `AGENTS.md` in your repo root:

```markdown theme={null}
# Notifyer WhatsApp Integration Rules

## Authentication
- Console API: `Authorization: Bearer ${NOTIFYER_API_TOKEN}` + `Origin: https://console.notifyer-systems.com`
- Chat API: `Authorization: ${NOTIFYER_API_TOKEN}` (no Bearer) + `Origin: https://chat.notifyer-systems.com`
- Base URL from `NOTIFYER_API_BASE_URL` env var (always HTTPS)

## 24-hour messaging window
- Free-text and media can only be sent if the recipient messaged us within the last 24 hours
- If window is closed, use a template message
- Check window via GET /api:bVXsw_FD/web/recipient — look at expiration_timestamp

## Coexistence and webhooks
- Do NOT tell users to delete the WhatsApp Business app. Meta WhatsApp Coexistence is supported.
- Webhooks fire for incoming AND outgoing messages, including hand-typed WhatsApp Business app replies.
- Payload: `incoming_message` (boolean), `send_by` (`WhatsApp App` | teammate name | automation), `was_message_by_human` (boolean)
- Docs: https://docs.whatsable.app/guides/notifyer-system/api/incoming-message

## Safe PATCH pattern
- Before PATCH /web/recipient/:id, always GET the full record first
- Include all existing fields in the PATCH body (name, phone_number, phone_number_string,
  global_label, is_ai_assistant, note) to prevent accidental data wipe

## Environment variables
- NOTIFYER_API_BASE_URL — required
- NOTIFYER_API_TOKEN — required, JWT from login
- Never commit tokens to Git
```

***

## Example Lovable prompts

With the project knowledge or `AGENTS.md` in place, use Lovable's Agent mode to build Notifyer-powered features:

### Send a WhatsApp message from a form

```
Add a "Send WhatsApp" button to the CustomerDetail page.
When clicked, it should call a Supabase Edge Function that sends a WhatsApp text message
via the Notifyer Chat API to the customer's phone number.
Use NOTIFYER_API_BASE_URL and NOTIFYER_API_TOKEN from environment variables.
Only send if the 24-hour window is open; otherwise show an error: "Window closed — use a template."
```

### Send a template when window is closed

```
In the CustomerDetail page, add a "Send Reminder" button.
The Edge Function should first check the recipient's expiration_timestamp.
If the 24h window is open, send a free-text message.
If closed, send the payment_reminder WhatsApp template instead.
Both paths use the Notifyer Chat API with the correct auth header (no Bearer prefix).
```

### Broadcast from the dashboard

```
Add a "Send Broadcast" section to the Marketing page.
It should let the user pick an approved template from a dropdown (fetched from
GET /api:AFRA_QCy/templates_web on the Notifyer Console API with Bearer auth),
upload a CSV of phone numbers, and trigger a broadcast via the Notifyer API.
```

### Webhook receiver

```
Create a Supabase Edge Function at /notifyer-webhook that receives POST requests
from Notifyer's IO webhook. Validate the HMAC-SHA256 signature using NOTIFYER_WEBHOOK_SECRET.
The webhook fires for incoming AND outgoing messages (including replies typed in the
WhatsApp Business app — coexistence is supported; do not tell users to delete the app).
Insert a row into the messages table with:
  { phone, body, direction: incoming_message ? "inbound" : "outbound",
    send_by, was_message_by_human, received_at }
When incoming_message is false, send_by is "WhatsApp App" (phone), a teammate name
(Notifyer inbox), or an automation name.
```

### Label and handoff from the app UI

```
In the ConversationView component, add two buttons:
1. "Assign to Human" — calls PATCH /api:bVXsw_FD/web/recipient/:id with is_ai_assistant: false
   using the Notifyer Chat API (Authorization: <token> without Bearer).
2. "Assign Label" — shows a dropdown of available labels and calls the same PATCH endpoint
   with the updated global_label array.
Both should fetch the full recipient record first before patching.
```

## Incoming and outgoing WhatsApp messages

Notifyer delivers **both incoming and outgoing** messages to your webhook or automation trigger — including messages typed by hand in the **WhatsApp Business app** on your phone.

This is possible because Notifyer supports [Meta WhatsApp Coexistence](/guides/notifyer-system/embedding-process#whatsapp-coexistence). You keep using WhatsApp Business on your phone; those hand-typed replies still reach an external webhook and can start an automation. They are not limited to the Notifyer web inbox.

<Frame>
  <iframe title="Trigger n8n workflows with WhatsApp messages" />
</Frame>

The payload is the same whether you use [n8n](/guides/notifyer-system/n8n-overview), [Make](/guides/notifyer-system/make-overview), [Zapier](/guides/notifyer-system/zapier-overview), or a [custom webhook](/guides/notifyer-system/api/incoming-message). [Watch the walkthrough on YouTube](https://www.youtube.com/watch?v=UfW-KwS4gBI).

### Direction, sending system, and team member

Use these three fields to tell *what happened* and *who sent it*:

<ResponseField name="incoming_message" type="boolean">
  `true` when a contact sent a message **to** your business. `false` when your business sent a message **to** the contact (outgoing). Filter on this field to run logic only for one direction.
</ResponseField>

<ResponseField name="send_by" type="string">
  Which system or person sent an **outgoing** message:

  | `send_by` value | Meaning |
  | - | - |
  | `WhatsApp App` | Typed by hand in the WhatsApp Business app on a phone |
  | A team member's name (for example `Axel Meta`) | Sent from the Notifyer chat inbox by that logged-in user |
  | An automation or app name (Make, Zapier, n8n, API, bot) | Sent by that integration or bot |

  Empty or omitted on incoming messages.
</ResponseField>

<ResponseField name="was_message_by_human" type="boolean">
  `true` when a person sent the message (WhatsApp Business app or Notifyer chat inbox). `false` when a bot or automation sent it. Combine with `send_by` to see both *whether* a human sent it and *which teammate or system* did.
</ResponseField>

### Example payload: message typed on the phone

This is the JSON Notifyer POSTs when someone types a reply in the WhatsApp Business app. `incoming_message` is `false`, `send_by` is `"WhatsApp App"`, and `was_message_by_human` is `true`.

```json theme={null}
{
  "last_messages": "[{\"type\":\"bot\",\"content\":\"Hello n8n\",\"timestamp\":\"2026-08-15T12:24:47.000Z\",\"content_type\":\"text\"},{\"type\":\"user\",\"content\":\"hi\",\"timestamp\":\"2026-08-12T12:27:42.746Z\",\"content_type\":\"text\"}]",
  "conversation_paragraph": "Bot (12:24:47 PM): Hello n8n ; User (12:27:42 PM): hi",
  "phone_number": 14155552671,
  "recipient_name": "Alex Martinez",
  "user_id": "158c59e1-ea85-4d0b-b70c-65328ba67a8e",
  "last_message_of_user": "hi",
  "last_message_of_bot": "Hello n8n",
  "message_type": "text",
  "user_last_message_time": 1786722580,
  "bot_last_message_time": 1786797014,
  "attachment_url": null,
  "note": "email: alex\nName: Alex",
  "note_automation": "email: alex\nName: Alex",
  "labels": "n8n, webhook-test",
  "incoming_message": false,
  "send_by": "WhatsApp App",
  "was_message_by_human": true
}
```

<Note>
  `last_message_of_bot` is the last message **your business** sent — whether a human typed it in the WhatsApp Business app or the Notifyer inbox, or a bot/automation sent it. `last_messages` is a JSON **string** of the last \~20 messages (parse it before iterating). `phone_number` may arrive as a number rather than a string.
</Note>

When the same person sends from the Notifyer chat inbox instead of the phone app, the payload is identical except:

```json theme={null}
{
  "incoming_message": false,
  "send_by": "Axel Meta",
  "was_message_by_human": true
}
```

***

## Using Plan mode before building

For complex integrations, click **Plan** next to the message input to switch to Plan mode before any code is written. Plan mode never modifies your code — it only reasons and proposes an approach.

```
I want to integrate Notifyer WhatsApp messaging into this app.
We need to: send template messages when a new order is created, receive inbound
AND outbound messages via webhook (including WhatsApp Business app replies;
incoming_message, send_by, was_message_by_human), and show chat history in the CustomerDetail page.
What's the best architecture using Supabase Edge Functions?
```

When you're happy with the plan, approve it and Lovable automatically switches to **Agent mode** to implement each piece. The approved plan is saved to `.lovable/plan.md` in your project.

***

## Environment variables by backend

Lovable supports two distinct backends. The env var workflow is different for each.

<Tabs>
  <Tab title="Lovable Cloud (built-in backend)">
    Lovable Cloud is Lovable's own full-stack hosting platform — no external Supabase account needed. It handles the backend automatically.

    When Lovable generates an Edge Function that calls the Notifyer API, instruct it to read secrets from environment variables:

    ```
    Store NOTIFYER_API_BASE_URL and NOTIFYER_API_TOKEN as secrets in
    Lovable Cloud and read them inside the Edge Function with
    Deno.env.get("NOTIFYER_API_TOKEN").
    ```

    Lovable Cloud manages the secret injection automatically as part of the Cloud environment. You can review and manage Cloud settings via **Connectors → App connectors → Lovable Cloud → Manage permissions**.
  </Tab>

  <Tab title="Supabase integration (external Supabase account)">
    If your project uses the Supabase integration (you connected your own Supabase project via **Project settings → Integrations → Supabase**):

    1. Open your **Supabase dashboard** → **Settings → Edge Functions → Secrets**
    2. Add `NOTIFYER_API_BASE_URL` and `NOTIFYER_API_TOKEN` as secrets
    3. Reference them in Edge Functions with `Deno.env.get("NOTIFYER_API_TOKEN")`

    <Warning>
      Never pass `NOTIFYER_API_TOKEN` as a hardcoded string in Edge Function code — it would be visible in your GitHub repository.
    </Warning>
  </Tab>

  <Tab title="External / self-hosted deployment">
    If you've exported your Lovable project to GitHub and are hosting it yourself, configure environment variables through your host's standard mechanism (e.g. Vercel env vars, Railway secrets, `.env` on a VPS).
  </Tab>
</Tabs>

***

## Important constraints

<Warning>
  These operations **cannot** be done via Lovable or any API — they require the Notifyer Console web UI:

  * Initial WhatsApp number connection (embedded signup / QR scan)
  * Billing and Stripe plan changes
  * Meta template approval (timing is controlled by Meta, not the API)
</Warning>

***

## Related pages

* [Quickstart](/guides/notifyer-system/agent-skills/quickstart)
* [Auth & environment](/guides/notifyer-system/agent-skills/auth-and-env)
* [Security](/guides/notifyer-system/agent-skills/security)
* [Using with Cursor](/guides/notifyer-system/agent-skills/platforms/cursor) — install skills locally if you work on the Lovable project in Cursor
* [Lovable Agent mode docs](https://docs.lovable.dev/features/agent-mode)
* [Lovable Knowledge docs](https://docs.lovable.dev/features/knowledge)
* [Lovable Plan mode docs](https://docs.lovable.dev/features/plan-mode)


# Quickstart
Source: https://docs.whatsable.app/guides/notifyer-system/agent-skills/quickstart

Install Notifyer Agent Skills and run the first health checks and API calls.

<Tip>
  This guide assumes **Node.js 18+**. The skills use native `fetch` and ESM and intentionally avoid third-party dependencies.
</Tip>

## Choose an installation path

<Tabs>
  <Tab title="Install via AgentSkills CLI (recommended)">
    If your agent supports the AgentSkills ecosystem, install directly from the repository:

    <CodeGroup>
      ```bash theme={null}
      # Interactive — choose which skills to install
      npx skills add whatsable/whatsapp-business-agent-skills
      ```

      ```bash theme={null}
      # Install all 3 skills at once (no prompt)
      npx skills add whatsable/whatsapp-business-agent-skills --all
      ```

      ```bash theme={null}
      # Install only one skill
      npx skills add whatsable/whatsapp-business-agent-skills --skill chat-notifyer
      ```
    </CodeGroup>

    <Tip>
      If your goal is “just make my agent fully capable in Notifyer”, use `--all` so it can load `setup-notifyer`, `automate-notifyer`, and `chat-notifyer` as needed.
    </Tip>
  </Tab>

  <Tab title="Manual clone (scripts only)">
    ```bash theme={null}
    git clone https://github.com/Whatsable/whatsapp-business-agent-skills
    cd whatsapp-business-agent-skills
    ```

    Each skill is self-contained under `skills/<skill-name>/`.
  </Tab>
</Tabs>

## Set required environment variables

You need:

* `NOTIFYER_API_BASE_URL`
* `NOTIFYER_API_TOKEN` (JWT from `setup-notifyer/scripts/login.js`)

```bash theme={null}
export NOTIFYER_API_BASE_URL="https://api.insightssystem.com"
export NOTIFYER_API_TOKEN="eyJ..."  # set after login
```

For deeper detail (auth modes, origins, and safety), see [Auth & environment](/guides/notifyer-system/agent-skills/auth-and-env).

## Log in and capture a token

```bash theme={null}
cd skills/setup-notifyer
node scripts/login.js --email you@example.com --password "YourPassword@1"
```

The output includes `authToken`. Export it:

```bash theme={null}
export NOTIFYER_API_TOKEN="eyJ..."
```

<Tip>
  If you’re also running the Notifyer Chat frontend locally for UI testing, use the pinned dev URL `http://localhost:5173/` as documented in `chat.notifyer_frontend/README.md`.
</Tip>

## Run a pre-flight health check

Before running any automation or chat script, validate the account is in a healthy state.

```bash theme={null}
cd skills/setup-notifyer
node scripts/doctor.js --pretty
```

`doctor.js` validates, in one command:

* Base URL is set and HTTPS
* Token is valid (`/auth/me`)
* WhatsApp connection is usable (`isConnected` + degraded detection)
* Subscription is in an allowed state

## Verify identity + WhatsApp connection

```bash theme={null}
node scripts/get-me.js --pretty
node scripts/get-connection-status.js --pretty
```

## Next steps (pick your goal)

* **Workspace setup & infra**: [`setup-notifyer`](/guides/notifyer-system/agent-skills/setup-notifyer)
* **Automation primitives**: [`automate-notifyer`](/guides/notifyer-system/agent-skills/automate-notifyer)
* **Live chat ops**: [`chat-notifyer`](/guides/notifyer-system/agent-skills/chat-notifyer)

If you’re stuck, see [Troubleshooting](/guides/notifyer-system/agent-skills/troubleshooting).


# Security
Source: https://docs.whatsable.app/guides/notifyer-system/agent-skills/security

Security model and best practices for using Notifyer Agent Skills, JWTs, Developer API keys, and webhook signatures.

## Secrets you must protect

| Secret | What it does | Treat as |
| - | - | - |
| `NOTIFYER_API_TOKEN` (JWT) | Authenticates Console + Chat script access | Session secret |
| Developer API key | Authenticates Make/Zapier/n8n + developer send endpoints | Long-lived API secret |
| Webhook signature secret | Validates inbound webhook authenticity (HMAC) | Long-lived signing secret |

<Warning>
  Do not store any of these in Git, client-side code, screenshots, or public pastebins.
</Warning>

## Recommended storage

* **Local dev**: `.env` (gitignored) or your shell profile + a password manager
* **CI/CD**: secrets manager (GitHub Actions secrets, Vercel env, 1Password, etc.)
* **Servers**: environment variables provisioned at deploy time

## CLI operational security

### Avoid leaking passwords via process lists

When using `--password` flags, be aware flags can show up in process lists while the script is running. On shared machines, consider running login in a private terminal session and avoid persistent command history.

### Avoid logging tokens

Some scripts print structured JSON to stdout by design. If you pipe outputs into logs, redact secrets.

## Webhook authenticity

If you enable `--signature` during webhook creation, Notifyer generates an HMAC secret. You should:

* Store it immediately
* Verify webhook payload signatures on your server
* Rotate by creating a new webhook (if rotation is needed)

<Tip>
  If you lose the signature secret, you generally cannot retrieve it again. Create a new webhook.
</Tip>

## Least privilege + operational controls

* Prefer using an **Admin** token only when required (team, labels, bot defaults).
* Use `setup-notifyer/scripts/doctor.js` as a gating step before production automation runs.
* For incident response, revoke/rotate credentials in the UI where available and update your secrets store.


# setup-notifyer
Source: https://docs.whatsable.app/guides/notifyer-system/agent-skills/setup-notifyer

Account + workspace setup scripts: login, health checks, WhatsApp connection status, plans, team/roles, labels, and Developer API key.

<Tip>
  Start here. `setup-notifyer` provides authentication and **pre-flight validation** used by all other skills.
</Tip>

## What this skill covers

`setup-notifyer` is used for:

* Creating accounts and logging in (JWT acquisition)
* Verifying token, plan status, and WhatsApp connection health
* Managing team members, roles, and label assignment
* Creating and managing workspace labels + keywords
* Retrieving the **Developer API key** used by Make/Zapier/n8n modules

## Setup

```bash theme={null}
cd skills/setup-notifyer
```

Set env vars (see [Auth & environment](/guides/notifyer-system/agent-skills/auth-and-env)):

```bash theme={null}
export NOTIFYER_API_BASE_URL="https://api.insightssystem.com"
export NOTIFYER_API_TOKEN="eyJ..."  # after login
```

## Core workflows

### 1) Login (get a JWT)

```bash theme={null}
node scripts/login.js --email you@example.com --password "YourPassword@1"
```

Export `authToken` into `NOTIFYER_API_TOKEN`.

### 2) Pre-flight health check (recommended before any automation)

```bash theme={null}
node scripts/doctor.js --pretty
```

This checks:

* Base URL is HTTPS
* Token is valid via `/auth/me`
* WhatsApp connection is **connected** and not **degraded**
* Plan is in an allowed state

### 3) WhatsApp connection checks

```bash theme={null}
node scripts/get-connection-status.js --pretty
```

If connection state is stale after UI onboarding:

```bash theme={null}
node scripts/refresh-connection.js --pretty
```

<Warning>
  Initial WhatsApp connection (embedded signup / QR scan) is **browser-only**. Scripts can manage a connection *after* it exists, but cannot complete first-time setup. You do **not** need to delete the WhatsApp Business app — [coexistence](/guides/notifyer-system/embedding-process#whatsapp-coexistence) is supported.
</Warning>

### 4) Plans & usage

```bash theme={null}
node scripts/list-plans.js --pretty
node scripts/get-user-plan.js --pretty
```

<Tip>
  If you’re guiding an automation that needs integrations or bots, gate it by plan status first using `get-user-plan.js`.
</Tip>

### 5) Team & roles

```bash theme={null}
node scripts/list-members.js --labels --pretty
node scripts/invite-member.js --name "John" --email john@co.com --password "Pass@1" --role "Team Member" --labels "Sales,Support"
node scripts/update-member.js --id <id> --role Admin
node scripts/remove-member.js --id <id> --confirm
```

Roles:

* `Admin`
* `Team Member (All Labels)`
* `Team Member`

### 6) Labels & keywords

```bash theme={null}
node scripts/list-labels.js --pretty
node scripts/create-label.js --label "Support" --keywords "help,issue,ticket"
node scripts/update-label-keywords.js --id 5 --add "urgent"
node scripts/delete-label.js --id 5 --confirm
```

## Developer API key (Make/Zapier/n8n)

Retrieve the Developer API key:

```bash theme={null}
node scripts/get-api-key.js --pretty
```

<Warning>
  The Developer API key is **not** the JWT token. It is used as `Authorization: <api_key>` (raw) by external tools and developer endpoints.
</Warning>

## Script index (high-signal)

* **Auth**: `create-account.js`, `login.js`, `get-me.js`
* **Health**: `doctor.js`
* **Connection**: `get-connection-status.js`, `refresh-connection.js`
* **Plans**: `list-plans.js`, `get-user-plan.js`
* **Team**: `list-members.js`, `invite-member.js`, `update-member.js`, `remove-member.js`
* **Labels**: `list-labels.js`, `create-label.js`, `update-label-keywords.js`, `delete-label.js`
* **API key**: `get-api-key.js`

## Next

* Move to automation: [`automate-notifyer`](/guides/notifyer-system/agent-skills/automate-notifyer)
* Or operate live chat: [`chat-notifyer`](/guides/notifyer-system/agent-skills/chat-notifyer)


# Troubleshooting
Source: https://docs.whatsable.app/guides/notifyer-system/agent-skills/troubleshooting

Diagnose common failures (401, degraded WhatsApp connection, plan blocks, template status, 24h window, webhooks).

## First command to run

Before debugging anything else:

```bash theme={null}
cd skills/setup-notifyer
node scripts/doctor.js --pretty
```

It validates the most common root causes in one pass (base URL, token, connection, plan).

## Authentication failures (HTTP 401 / 403)

### Token expired or missing

Symptoms:

* Most scripts return 401
* `get-me.js` fails

Fix:

```bash theme={null}
cd skills/setup-notifyer
node scripts/login.js --email you@example.com --password "YourPassword@1"
export NOTIFYER_API_TOKEN="eyJ..."
node scripts/get-me.js --pretty
```

### Wrong auth mode header

Symptoms:

* Console scripts work, chat scripts fail (or vice versa)

What to know:

* Console uses `Authorization: Bearer <jwt>`
* Chat uses `Authorization: <jwt>` (raw)

The skills handle this automatically, but custom wrappers often get it wrong. See [Auth & environment](/guides/notifyer-system/agent-skills/auth-and-env).

## WhatsApp connection issues

### `isConnected: false`

Run:

```bash theme={null}
cd skills/setup-notifyer
node scripts/get-connection-status.js --pretty
```

If the number was just connected in the UI, refresh:

```bash theme={null}
node scripts/refresh-connection.js --pretty
```

<Warning>
  If this is a first-time setup, you must complete the embedded signup / QR scan in the console UI. It is not scriptable.
</Warning>

### `degraded: true`

This can mean Meta returned hidden errors that may cause silent send failures. Treat it as “not healthy” until resolved. Use the console UI to resolve Meta-side issues, then re-check status.

## Plan blocks (features not available)

Symptoms:

* Developer API key exists but integrations/bots fail
* Bot creation fails due to missing OpenAI key/settings

Check:

```bash theme={null}
cd skills/setup-notifyer
node scripts/get-user-plan.js --pretty
```

## Template issues

### Template not usable yet

Templates must be `APPROVED` by Meta before use in automation/broadcasts.

```bash theme={null}
cd skills/automate-notifyer
node scripts/list-templates.js --pretty
node scripts/list-templates.js --status approved --pretty
```

## Message send failures in chat

### 24-hour window is closed

If free text fails, check:

```bash theme={null}
cd skills/chat-notifyer
node scripts/get-recipient.js --phone 14155550123 --pretty
```

Fix: use a template send (`send-template.js`) until the recipient messages again.

## Webhook issues

### Wrong webhook type / id

* Dev webhook id is **integer**
* IO webhook id is a **text UUID**

```bash theme={null}
cd skills/automate-notifyer
node scripts/list-webhooks.js --type dev --pretty
node scripts/list-webhooks.js --type io --pretty
```

### Signature secret lost

If you created a webhook with `--signature`, the secret is shown only once. If you didn’t store it, create a new webhook and deprecate the old one.


# Use cases
Source: https://docs.whatsable.app/guides/notifyer-system/agent-skills/use-cases

End-to-end playbooks: onboarding, templates, broadcasts, chat triage, and webhook-driven operations.

## Workspace onboarding automation

Goal: create a clean, operational workspace baseline that’s ready for automation and live chat.

```bash theme={null}
# 1) Authenticate
cd skills/setup-notifyer
node scripts/login.js --email you@example.com --password "YourPassword@1"
export NOTIFYER_API_TOKEN="eyJ..."

# 2) Validate health
node scripts/doctor.js --pretty

# 3) Create labels
node scripts/create-label.js --label "Sales" --keywords "pricing,quote,buy"
node scripts/create-label.js --label "Support" --keywords "help,issue,ticket"
node scripts/create-label.js --label "VIP"

# 4) Invite team
node scripts/invite-member.js --name "Amina" --email amina@co.com --password "Pass@1" --role "Team Member" --labels "Support"
node scripts/invite-member.js --name "Omar" --email omar@co.com --password "Pass@1" --role "Team Member" --labels "Sales"

# 5) Fetch Developer API key (for Make/Zapier/n8n)
node scripts/get-api-key.js --pretty
```

## Template lifecycle management

Goal: submit a template, track approval, then use it in a broadcast.

```bash theme={null}
cd skills/automate-notifyer

# Create template
node scripts/create-template.js \
  --name order_shipped \
  --category UTILITY \
  --body "Hi {{1}}, your order {{2}} has shipped!" \
  --variables '{"1":"John","2":"#12345"}'

# Poll status (also syncs PENDING from Meta)
node scripts/list-templates.js --pretty

# Use only after approved
node scripts/list-templates.js --status approved --pretty
```

## Broadcast campaign management

Goal: test + upload audience + schedule a bulk send.

```bash theme={null}
cd skills/automate-notifyer

node scripts/create-broadcast.js \
  --name "Feb Promo" \
  --template-id 42 \
  --test-phone "+14155550123" \
  --recipients ./recipients.csv \
  --schedule "01/02/2026 10:00" \
  --delivery-mode smart \
  --delivery-size 4

node scripts/list-broadcasts.js --status upcoming --pretty
```

## Live support triage loop

Goal: find unread high-priority conversations, take over, respond, document, and return to bot.

```bash theme={null}
cd skills/chat-notifyer

# 1) Find unread VIP
node scripts/filter-recipients-by-label.js --labels "VIP" --status unread --pretty

# 2) Load context
node scripts/get-recipient.js --phone 14155550123 --pretty
node scripts/get-notes.js --phone 14155550123 --pretty
node scripts/get-conversation.js --phone 14155550123 --pretty

# 3) Take over + respond
node scripts/set-handoff.js --phone 14155550123 --mode human
node scripts/send-text.js --phone 14155550123 --text "Hi — I’m looking into this now."

# 4) Record internal context + route
node scripts/add-note.js --phone 14155550123 --append "Escalated — awaiting refund approval"
node scripts/assign-label.js --phone 14155550123 --label "Escalated"

# 5) Return to bot
node scripts/set-handoff.js --phone 14155550123 --mode bot
```

## Pre-flight gating before any send

These checks prevent most “why didn’t it send?” incidents.

```bash theme={null}
# Workspace health: token + connection + plan
cd skills/setup-notifyer
node scripts/doctor.js --pretty

# Recipient window state (templates always allowed; text/media need window open)
cd ../chat-notifyer
node scripts/get-recipient.js --phone 14155550123 --pretty
```

## Webhook-driven automation setup

Goal: configure a webhook endpoint that receives **incoming and outgoing** WhatsApp messages (including replies typed in the WhatsApp Business app) and secure it with HMAC signature.

```bash theme={null}
cd skills/automate-notifyer

node scripts/create-webhook.js --type dev \
  --url "https://my.app/webhook" \
  --incoming --outgoing --signature

node scripts/list-webhooks.js --type dev --pretty
```

`--outgoing` is required for phone-app and inbox replies. Payload fields: `incoming_message`, `send_by`, `was_message_by_human`. See [Message webhooks](/guides/notifyer-system/api/incoming-message) and [coexistence](/guides/notifyer-system/embedding-process#whatsapp-coexistence).


# Bot Configuration
Source: https://docs.whatsable.app/guides/notifyer-system/ai-chatbot/configuration

Field-by-field reference for every AI agent setting in Whatsable — identity, knowledge, sendable files, instructions, response, labels, handoff, and follow-ups.

<Tip>
  You can create as many agents as your plan allows and assign them per WhatsApp number. The configuration form is the same whether you are creating a new agent or editing an existing one.
</Tip>

## Opening the form

* **Create**: From the [AI Chatbots](/guides/notifyer-system/ai-chatbot/overview) dashboard, click **Create agent**.
* **Edit**: Click **Edit** on any existing agent. The form loads with saved values pre-filled.

The editor sidebar follows this order:

1. **Agent identity**
2. **Knowledge base**
3. **Files it can send**
4. **Custom instructions**
5. **Response settings**
6. **Labels**
7. **Notifications**
8. **Follow-ups**
9. **Review** (readiness checklist — not a separate saved field)

New agents start as **Draft**. Activate or archive them from the dashboard list, not from this form body.

***

## Agent identity

Defines who the agent is for your team. Customers never see these fields.

<ResponseField name="Name" type="string">
  An internal label operators see in the inbox and on the assign menu (for example `Sales concierge`). Max **60** characters.

  Customers never see this name.
</ResponseField>

<ResponseField name="Mission" type="string">
  One sentence the agent works from on every reply — what the job is (pricing, booking, qualifying leads). Max **20,000** characters.

  Rules and exceptions belong in **Custom instructions**, not here.

  **Good example:** `Qualify inbound leads, answer pricing questions from our published tiers, and book a demo when the customer is ready.`
</ResponseField>

<Info>
  “Default” is **per WhatsApp number**, not a single flag on the agent itself. An agent becomes the org-wide default when every connected number points at it (dashboard **Set as default** / number assignment).
</Info>

***

## Knowledge base

Price lists, policies, and product sheets the agent answers from. Knowledge is **optional for Save** — an agent can still be saved with only Name, Mission, and Instructions — but without knowledge it answers only from the mission and custom instructions.

### Data sources (file uploads)

<ResponseField name="Add data source" type="file[]">
  Upload documents Whatsable parses into text for the agent. Supported formats:

  | Format | Notes |
  | - | - |
  | `.pdf` | Text is extracted; image-only PDFs yield no content |
  | `.txt` | Plain text, read as-is |
  | `.md` | Markdown |
  | `.csv` | Useful for catalogues or FAQ tables |
  | `.docx` | Word documents; text extracted automatically |

  **Limits:** each file must be within the media size cap (typically **10 MB**). On create, files stay **staged** until the first successful save, then upload.

  Statuses you may see: **Processing**, **Ready**, **Failed**, or **Waiting** (staged). Failed reasons are closed classes such as unsupported type, timeout, unreadable, or empty — never a raw parser dump.
</ResponseField>

<Warning>
  If the agent is **Archived**, knowledge uploads are disabled until you restore it.
</Warning>

### Written knowledge

<ResponseField name="Anything the files do not cover?" type="string">
  Short facts that belong in text rather than a file: hours, a delivery price, a promise you never make. Max **200,000** characters.

  Leave this empty if uploads cover everything. Empty knowledge does **not** block Save (it only affects the readiness score).
</ResponseField>

***

## Files the agent can send

Distinct from the knowledge base. **Knowledge is what the agent knows. Files are what it can send** — the agent never reads the file bytes; it chooses a file only from the description you write.

Cap: **10** sendable files per agent.

<ResponseField name="What the file you are adding is for" type="string">
  Required to add a file. Max **1,000** characters. This sentence is the only thing the model uses to decide when to send the attachment.

  **Example:** `The 2026 price list, with delivery times for each region — send when a customer asks for pricing in writing.`
</ResponseField>

<Warning>
  A sendable file **without a description** cannot be chosen by the agent. Write a clear description before you rely on the agent to send that file.
</Warning>

<ResponseField name="What to call the file you are adding" type="string">
  Optional display name (max **120** characters). Falls back to the original filename when empty. Editable later without re-uploading.
</ResponseField>

<ResponseField name="The agent may send this file" type="boolean">
  Per-file switch. Turn off to keep the file uploaded but stop the agent from sending it, without deleting the row.
</ResponseField>

<Warning>
  Archived agents cannot accept new sendable files until restored. On create, chosen files stay staged until the first save.
</Warning>

***

## Custom instructions

<ResponseField name="Instructions" type="string">
  Rules for every reply this agent sends. The mission says what the job is; these lines say how to do it. **Required to Save** in the current editor. Max **80,000** characters.

  Write **one rule per line**. Typical uses:

  * Topics the agent must never discuss
  * Questions it must ask before booking or quoting
  * Formatting preferences
  * When to add or remove a label (name the label exactly as it appears under **Labels**)

  **Example:**

  ```
  Always ask for the customer's order number before discussing a refund.
  Never mention competitor products.
  If you do not know, say so — do not invent a price.
  Add Hot lead when they ask to reserve or hold stock.
  ```
</ResponseField>

***

## Response settings

Controls how the agent communicates and when it returns after a human reply — not what facts it knows.

### How should the agent sound?

<ResponseField name="Tone" type="string">
  Free-text voice for ordinary replies (max **300** characters). Blank is allowed; when blank at runtime the platform falls back to a friendly default.

  Four presets fill the input (you can still edit the text afterward):

  | Preset | Feel |
  | - | - |
  | **Friendly** | Warm, informal |
  | **Professional** | Clipped, precise |
  | **Balanced** | Middle ground |
  | **Enthusiastic** | High energy |

  Follow-up voice is steered separately under **Follow-ups** → **What to say in a follow-up**.
</ResponseField>

### How long should the agent wait before it sends a reply?

<ResponseField name="How long should the agent wait before it sends a reply?" type="integer (seconds)">
  Debounce after the customer writes, before the agent’s answer goes out. Range **0–300** seconds (slider). Default **5**.

  **0 is legal** — the turn can start immediately. A short wait feels more human and lets several quick messages batch into one reply.

  This wait **does not** apply to proactive follow-ups.
</ResponseField>

<Tip>
  **Recommended starting point:** about 8–12 seconds for most businesses. Use a low value for high-volume queues; raise it when customers tend to send several short messages before finishing their question.
</Tip>

### Once you reply by hand

<ResponseField name="Once you reply by hand" type="enum">
  What happens after you or a teammate reply manually (including from the WhatsApp Business app). Options:

  | Option | Behaviour |
  | - | - |
  | **The agent stays off until someone turns it back on** (`never`) | Default. Agent stays quiet on that chat until re-enabled. |
  | **The agent resumes when the customer starts a new conversation** (`new_session`) | Stays off for the current session; returns on a new conversation. |
  | **The agent resumes after a set time** (`timer`) | Stays quiet for the duration you set, then can answer again. |
</ResponseField>

<ResponseField name="Resume after (minutes)" type="integer (minutes)">
  Shown only when the policy is **The agent resumes after a set time**. Range **1–10,080** minutes (1 minute to 7 days). Required when that policy is selected.

  The quiet period restarts if you write again. Replies from the Whatsable dashboard vs the mobile app may differ in how the timer is started — see [Shared team inbox](/guides/notifyer-system/team-inbox) for operator behaviour in the live chat.
</ResponseField>

***

## Labels

Lets the agent add or remove conversation labels you grant it. Powers default **on**.

<ResponseField name="Let this agent add labels" type="boolean">
  When on, the agent may tag conversations according to your label instructions and grants.
</ResponseField>

<ResponseField name="Let this agent remove labels" type="boolean">
  When on, the agent may remove granted labels when instructions say so.
</ResponseField>

<ResponseField name="Most labels to add in one reply" type="integer | null">
  Shown when add is enabled. Range **1–5**. Leave unset (**Use the maximum**) to use the platform max of **5**.
</ResponseField>

<ResponseField name="Most labels to remove in one reply" type="integer | null">
  Same pattern as the add cap: **1–5**, or unset for the platform max of **5**.
</ResponseField>

<ResponseField name="Which labels this agent may use" type="enum">
  | Mode | Behaviour |
  | - | - |
  | **Every label** (`all`) | May use any label in the organization, including ones created later. Grant checkboxes appear selected and disabled. |
  | **Only the ones I pick** (`listed`) | May use only the labels you tick (max **20**). |
</ResponseField>

<Warning>
  If label powers are **on**, grant mode is **Only the ones I pick**, and **no labels are ticked**, the agent has nothing it can apply. The editor shows a readiness warning — labels will look broken until you grant at least one label or switch to **Every label**.
</Warning>

<ResponseField name="When to apply a label" type="string">
  Policy text the model reads every turn (max **10,000** characters). Describe the moment in plain language.

  **Example:** `Add Hot lead when they ask to hold stock. Remove it once they pay.`
</ResponseField>

***

## Notifications

When a customer wants a person, the agent steps back, the thread can be left unassigned, and a teammate can pick it up. Keywords catch explicit phrases; the situations box catches the rest.

There is **no** separate notification toggle on this form (including no “Human Agent Request Notification” control). Configure keywords and situations here; team alerting follows product handoff behaviour.

### Which words mean they want a person?

<ResponseField name="Which words mean they want a person?" type="string[]">
  Words or short phrases that, when present in a customer message, signal human assistance. Matching is **case-insensitive**.

  Limits: up to **25** keywords, each up to **120** characters.

  **Common examples:** `agent`, `human`, `speak to someone`, `real person`, `talk to a person`

  Add rows with **Add keyword**; remove with the control on each chip.
</ResponseField>

### Besides those words, when should it hand over?

<ResponseField name="Describe those situations" type="string">
  Plain-language situational escalation — anger, a large refund, a safety issue — even when no keyword matched. Max **10,000** characters. This is **policy for the model**, not a WhatsApp message body.

  **Example:** `Hand over when the customer is frustrated or angry; when discussing refunds over $500; when a product safety issue is reported; when three exchanges have not resolved the issue.`

  Leave blank if you only want keyword-based handoff.
</ResponseField>

<Info>
  Keywords and situations work together. Keywords catch explicit asks; situations catch contextual ones.
</Info>

***

## Follow-ups

Outbound chase when a conversation goes quiet after your side (or the agent) sent a WhatsApp message. Cadence fields appear only while follow-ups are enabled; turning the master switch off hides them in the UI but stored values are kept for when you turn it back on.

### Master switch

<ResponseField name="Follow up when a conversation goes quiet" type="boolean">
  Master switch. Off by default. When on, an unanswered outbound message can start a follow-up sequence inside the budget and window you set.
</ResponseField>

### Cadence

Enter delays as **days + hours + minutes** (they add up to a single minute total stored by the API).

<ResponseField name="Wait before the first follow-up" type="integer (minutes)">
  Delay from the unanswered outbound before the first follow-up. Range **1–43,200** minutes (**30 days**). Default **4 hours**. Must be **strictly less than** **Stop following up after**.
</ResponseField>

<ResponseField name="Stop following up after" type="integer (minutes)">
  Hard stop window from that same unanswered outbound. Range **2–129,600** minutes (**90 days**). Default **120 hours** (5 days).

  Every follow-up in the stretch must go out before this deadline.
</ResponseField>

<Note>
  Some on-screen validation copy may still mention a **30-day** window maximum. The platform contract allows up to **90 days**.
</Note>

<ResponseField name="How many follow-ups at most" type="integer">
  Budget for **one quiet stretch**, not a lifetime cap. Range **1–15**. Default **3**. If the customer replies and later goes quiet again, the budget can restart for the new stretch.
</ResponseField>

<ResponseField name="Minimum gap between follow-ups" type="integer (minutes)">
  Minimum spacing between one follow-up and the next. Range **0–43,200** minutes. Default **0**.
</ResponseField>

<ResponseField name="How to space them" type="enum">
  | Option | Behaviour |
  | - | - |
  | **Evenly** | Same gap between each follow-up |
  | **Sooner rather than later** | More of them early in the window (default) |
  | **Later rather than sooner** | More of them toward the deadline |

  A slot that would land in quiet hours or on a quiet day is **skipped**, not moved to the next open slot.
</ResponseField>

### Quiet hours, quiet days, and timezone

<ResponseField name="Do not send between" type="integer pair (0–23) | empty">
  Quiet-hour start and end (hours **0–23**). Leave **both** empty to allow any hour. Setting only one side clears both on save.
</ResponseField>

<ResponseField name="Do not send on" type="day toggles">
  Whole calendar days with no follow-ups (Sunday–Saturday), evaluated in the follow-up timezone.
</ResponseField>

<Warning>
  You cannot mark **all seven** weekdays as quiet. That would make every follow-up impossible; leave at least one day open, or turn follow-ups off.
</Warning>

<ResponseField name="Times are local to" type="IANA timezone">
  Timezone for quiet hours and quiet days (for example `Europe/Madrid`). Curated list plus stored or browser zones. Default **UTC**.
</ResponseField>

### Follow-up content and risky toggles

<ResponseField name="What to say in a follow-up" type="string">
  Used **only** when composing a follow-up, not ordinary replies. Max **12,000** characters. Say what to offer, what never to promise, and not to repeat the last message.
</ResponseField>

<ResponseField name="Keep following up even after a reply from your side" type="boolean">
  **On by default.** The agent can still follow up when a customer goes quiet after your side replied — from the inbox, the WhatsApp phone app, or your own API integration.
</ResponseField>

<Warning>
  **Keep following up even after a reply from your side** defaults to **on**. That is easy to miss: follow-ups can continue after a human, phone-app, or API outbound. Turn **off** so any outbound from your side ends follow-ups on that conversation for good.
</Warning>

<ResponseField name="Also follow up after a broadcast" type="boolean">
  **Off by default.**
</ResponseField>

<Warning>
  Turning **Also follow up after a broadcast** on can start a follow-up sequence for every recipient of a large blast. Keep it off unless you intentionally want that blast radius.
</Warning>

<ResponseField name="Let the agent write templates" type="boolean">
  **Off by default.** Outside the customer **24-hour** service window, WhatsApp only allows an approved template. With this on, the agent may propose a new template for Meta review on your WhatsApp account — enabling it is that consent. Templates it wrote are marked in your template list.
</ResponseField>

<Warning>
  A follow-up sent **outside the 24-hour window** is treated as **marketing**. It is subject to per-country limits and can affect your number’s quality rating. Enable **Let the agent write templates** only if you understand that trade-off; turning authoring on is Meta template-submit consent.
</Warning>

<ResponseField name="Templates it may propose per week" type="integer">
  Shown only when template authoring is on. Range **0–20**. Default **2**.
</ResponseField>

***

## Saving the configuration

Click **Save** when ready. The editor blocks save until:

1. **Name** is not empty
2. **Mission** is not empty
3. **Instructions** are not empty

Knowledge text and knowledge files are **not** save blockers (they affect readiness score only). Follow-up cadence fields are validated when follow-ups are enabled (ranges, first delay inside the window, quiet-day rules).

On success the agent is created or updated and you return to the AI agents list. New agents are not automatically the default — assign numbers or use **Set as default** on the dashboard.

<Note>
  Editing an agent does **not** rewrite conversations already in progress. Changes apply to the **next** message processed after save.
</Note>

### Related tools (not config fields)

* **Improve my agent** — helps organize mission, knowledge, instructions, handoff, and follow-up text before you apply them to the form.
* **Test your agent** — sandbox preview; nothing is sent to WhatsApp.
* **Review** — live readiness checklist before save.

***

## Next steps

<CardGroup>
  <Card title="AI Chatbots Overview" icon="bot" href="/guides/notifyer-system/ai-chatbot/overview">
    Dashboard actions, plan requirements, and how an agent processes messages end-to-end.
  </Card>

  <Card title="Shared team inbox" icon="inbox" href="/guides/notifyer-system/team-inbox">
    How operators take over a chat, resume policies, and live inbox behaviour.
  </Card>

  <Card title="Embedding Process" icon="plug" href="/guides/notifyer-system/embedding-process">
    Connect a WhatsApp number to your workspace before an agent can go live.
  </Card>
</CardGroup>


# AI Chatbots
Source: https://docs.whatsable.app/guides/notifyer-system/ai-chatbot/overview

Create and manage AI-powered WhatsApp assistants that handle customer conversations automatically — 24/7, on-brand, and with built-in human handoff.

<Tip>
  AI Chatbots are available on the **Pro** and **Agency** plans. Bulk Message subscribers will see an upgrade prompt instead of the bot dashboard.
</Tip>

## What are AI Chatbots?

Whatsable AI Chatbots are intelligent WhatsApp assistants powered by OpenAI. Each bot is trained with your business's own knowledge base and configured with a distinct personality, response style, and escalation rules — so customers get accurate, on-brand answers around the clock without any manual effort.

Once live, your bot:

* Reads each incoming WhatsApp message and generates a contextually accurate reply from your knowledge base
* Waits a configurable delay before sending (to feel human, not robotic)
* Detects human-handoff keywords and notifies your team the moment a customer asks to speak with someone
* Follows your custom escalation instructions for edge cases that go beyond the knowledge base

## Dashboard overview

The AI Chatbots dashboard (`/ai-bots`) lists every bot in your workspace as cards. The default bot always appears first with a **Default** star badge.

| Action | How |
| - | - |
| **Create a bot** | Click **Create New Bot** in the top-right corner |
| **Search** | Type in the search bar to filter bots by name |
| **Sort** | Use the sort dropdown to switch between **Newest** and **Oldest** |
| **Edit** | Click **Edit** on a bot card to open the full configuration form |
| **Set as default** | Click **Set Default** on any non-default bot card |
| **Duplicate** | Open the ⋮ menu → **Duplicate** — clones all settings as a new bot named `(Copy)` |
| **Delete** | Open the ⋮ menu → **Delete** — requires confirmation |

<Info>
  Only one bot can be **default** at a time. The default bot is the one Whatsable uses when no specific bot is assigned to an incoming conversation.
</Info>

## Plan requirements

<Warning>
  AI Chatbots require a **Pro** or **Agency** subscription. Workspace owners on the Bulk Message plan will see an upgrade notice in place of the bot dashboard. Visit your [Pricing Plans](/pricing-plans) page to upgrade.
</Warning>

| Plan | AI Chatbot access |
| - | - |
| Bulk Message | ✗ Not included |
| Pro | ✓ Full access |
| Agency | ✓ Full access + multiple phone numbers |

## How a bot processes a message

<Steps>
  <Step title="Message arrives">
    A customer sends a WhatsApp message to your connected number.
  </Step>

  <Step title="Delay window">
    The bot waits for the configured **Response Delay** (5–60 seconds). If the customer sends more messages in that window, they are batched and answered together.
  </Step>

  <Step title="AI generates a reply">
    The bot constructs a response using your **Business Mission**, **Knowledge Base**, **Custom Instructions**, and selected **Tone**.
  </Step>

  <Step title="Handoff check">
    If any **Trigger Keyword** is detected, or the **Custom Handoff Scenarios** condition is met, the bot stops replying and (optionally) sends you a notification.
  </Step>

  <Step title="Reply sent">
    The response is delivered to the customer over WhatsApp.
  </Step>
</Steps>

***

## Bot assignment in Notifyer Chat

Once you have bots configured, you control which bot handles each conversation from the [Notifyer Chat](https://chat.notifyer-systems.com/) interface. Assignment can be automatic (via the default bot) or manually overridden per conversation.

### Auto-assignment — the default bot

When a new inbound WhatsApp message starts a conversation and no specific bot has been manually assigned to that contact, the system automatically uses the bot marked as **Default** in your AI Chatbots dashboard.

<Info>
  Only one bot can be the default at a time. To change which bot handles new conversations automatically, go to the [AI Chatbots dashboard](/guides/notifyer-system/ai-chatbot/overview) and click **Set Default** on the bot you want.
</Info>

### Manual assignment per conversation

Every conversation in Notifyer Chat has a right-side contact panel. Inside that panel, under the **AI Assistant** section, is a **Bot Assign** dropdown.

<Steps>
  <Step title="Open the contact panel">
    In [Notifyer Chat](https://chat.notifyer-systems.com/), select any conversation. The contact details panel opens on the right.
  </Step>

  <Step title="Find the Bot Assign dropdown">
    Scroll to the **AI Assistant** section. Below the AI / Human Agent toggle you will see a **Bot Assign** selector showing either the currently assigned bot name or **Select Bot**.
  </Step>

  <Step title="Pick a bot">
    Click the dropdown and choose any bot from your workspace. The assignment updates immediately — the selected bot takes over responses for that conversation from the next incoming message.

    A checkmark appears next to the currently assigned bot so you always know which one is active.
  </Step>

  <Step title="Unassign if needed">
    If a bot is already assigned, the dropdown shows an **Unassign Bot** option at the top. Selecting it removes the bot assignment from that contact entirely and falls back to the default bot for any future messages.
  </Step>
</Steps>

### AI Assistant / Human Agent toggle

Alongside bot assignment, each conversation has a **Human Agent ↔ AI Assistant** toggle.

| Position | Behaviour |
| - | - |
| **AI Assistant** (on) | The assigned bot handles replies automatically; messages are also synced with connected automation tools (Zapier, Make, n8n, etc.) |
| **Human Agent** (off) | The bot stops replying; a team member takes over manually; automation sync is paused |

<Tip>
  When a customer triggers a **handoff keyword** or the bot's **Custom Handoff Scenarios** are met, flip this toggle to **Human Agent** to mute the bot and take control of the conversation yourself.
</Tip>

### Assignment priority summary

| Scenario | Bot used |
| - | - |
| New conversation, no manual assignment | Default bot |
| Manual assignment set in the contact panel | Manually assigned bot |
| Bot unassigned in the contact panel | Default bot (fallback) |
| Toggle switched to Human Agent | No bot — human only |

***

## Next steps

<CardGroup>
  <Card title="Bot Configuration" icon="sliders" href="/guides/notifyer-system/ai-chatbot/configuration">
    A field-by-field breakdown of every setting in the bot configuration form — identity, knowledge base, tone, delay, and handoff.
  </Card>

  <Card title="Embedding Process" icon="plug" href="/guides/notifyer-system/embedding-process">
    Connect a WhatsApp number to your workspace before deploying a bot.
  </Card>
</CardGroup>


# What Click-to-WhatsApp fields appear on Whatsable webhooks?
Source: https://docs.whatsable.app/guides/notifyer-system/api/ctwa-referral-fields

Map Click-to-WhatsApp referral on Whatsable webhooks: source_type, source_id, source_url, headline, body, media, ctwa_clid, and first-message context fields.

When someone taps **Send message** on a Click-to-WhatsApp ad (Facebook, Instagram, or WhatsApp Status) and writes to your number, Meta attaches a `referral` object to that inbound event. Whatsable forwards it on your custom webhook and on n8n, Make, and Zapier triggers — so you can see which creative, platform, and click produced the lead.

This page is the **dedicated field dictionary** for that `referral` object (and the first-message fields that ride alongside it). For the full inbound/outbound webhook payload, signature verification, and management API, use [Message webhooks](/guides/notifyer-system/api/incoming-message) — including the live [Click-to-WhatsApp ads](/guides/notifyer-system/api/incoming-message#click-to-whatsapp-ads) section.

## Prerequisites

* **Whatsable account** with a connected WhatsApp Business number (Embedded Signup / Coexistence supported — keep the WhatsApp Business app; do not uninstall it after connect).
* **Incoming** webhook or automation trigger enabled so contact → business messages reach your endpoint (custom HTTPS webhook, or [n8n](/guides/notifyer-system/n8n-overview) / [Make](/guides/notifyer-system/make-overview) / [Zapier](/guides/notifyer-system/zapier-overview)).
* **HTTPS endpoint** that accepts `POST` JSON and returns 2xx within \~10 seconds (same requirements as [Message webhooks](/guides/notifyer-system/api/incoming-message)).
* Optional: a CRM or Conversions API destination ready to store `ctwa_clid` and `source_id` as soon as they arrive (they usually appear **once**).

<Info>
  Integrations (Zapier / Make / n8n) require **Pro** or **Agency**. Custom webhooks follow your Developer settings. This page does not invent plan gates beyond that — see [plans Bulk Message / Pro / Agency](/guides/notifyer-system/plans-bulk-message-pro-agency).
</Info>

***

## What `referral` is for

| Goal | Fields to use |
| - | - |
| Group leads by campaign or creative | `source_id`, `headline` |
| See Facebook vs Instagram vs other | `source_url` (host is `instagram.com`, `facebook.com`, `fb.me`, …) |
| Show agents the ad the lead saw | `headline`, `body`, `image_url` / `video_url`, `media_type` |
| Send conversions back to Meta | `ctwa_clid` |

<Note>
  `referral` is typically present only on the **first inbound message** after the ad click. Later messages in the same chat usually omit it. Persist `ctwa_clid` and `source_id` (keyed on the contact's phone) as soon as they arrive.
</Note>

<Info>
  WhatsApp Status ad placements may omit `ctwa_clid`. Organic posts use `source_type: "post"` instead of `"ad"`.
</Info>

***

## Referral object — field dictionary

Look for `referral` as a **top-level** field on the Whatsable webhook payload, or at `entry[].changes[].value.messages[].referral` if the delivery includes the Meta Cloud API envelope.

| Exact key | Type | Meaning |
| - | - | - |
| `referral` | object | Present on incoming CTWA / post events; omitted on ordinary chats and most follow-ups |
| `referral.source_type` | string | `"ad"` or `"post"` |
| `referral.source_id` | string | Meta ad or post ID |
| `referral.source_url` | string | URL of the ad or post (platform is in the host) |
| `referral.headline` | string | Ad or post headline |
| `referral.body` | string | Ad or post body copy (may include emoji shortcodes such as `:fire:`) |
| `referral.media_type` | string | `"image"` or `"video"` |
| `referral.image_url` | string | Image creative URL when `media_type` is `"image"` (URLs can expire — copy assets you need to keep) |
| `referral.video_url` | string | Video creative URL when `media_type` is `"video"` |
| `referral.thumbnail_url` | string | Thumbnail URL for video creatives |
| `referral.ctwa_clid` | string | Click ID for Meta Conversions API attribution (`action_source: "business_messaging"`, `messaging_channel: "whatsapp"`) |
| `referral.welcome_message` | object | Optional. Welcome message configured on the ad, when Meta includes it. **Nested keys are not documented** — treat as an opaque object until product publishes children |

<Warning>
  Do **not** invent nested keys under `welcome_message` (for example `text` or `type`). Docs name the object only. Do **not** invent Meta-only names (`ads_context_data`, `source_app`, …) as Whatsable webhook fields. Do **not** confuse Facebook Lead Ads form webhooks with WhatsApp CTWA `referral`.
</Warning>

***

## First-message fields on the same event

Creative and attribution live under `referral.*`. The contact's first text rides on the **same** inbound payload in the usual message fields — useful for CRM notes and routing, not a separate inbox creative UI schema.

| Exact key | Role alongside `referral` |
| - | - |
| `incoming_message` | `true` on contact → business |
| `last_message_of_user` | Latest user text (sample: `"Quiero información"`) |
| `last_messages` | Recent thread (array or JSON string — parse before iterating) |
| `message_type` | e.g. `text` |
| `phone_number` | Contact digits (string or number) |
| `recipient_name` | Display name if available |
| `conversation_paragraph` | Human-readable summary |

Do **not** invent inbox-only creative field names. Whatsable documents webhook / trigger forwarding of `referral`; it does not publish a separate inbox “creative card” field list.

***

## Sample payload (Whatsable flattened shape)

```json theme={null}
{
  "last_messages": [
    {
      "type": "user",
      "content": "Quiero información",
      "timestamp": "2026-08-15T18:18:36.000Z",
      "content_type": "text"
    }
  ],
  "conversation_paragraph": "User (6:18:36 PM): Quiero información",
  "phone_number": "50655550100",
  "recipient_name": "Maria Lopez",
  "user_id": "9232fcef-a570-4a2c-b46b-6cab53aec304",
  "last_message_of_user": "Quiero información",
  "last_message_of_bot": "",
  "message_type": "text",
  "incoming_message": true,
  "send_by": "",
  "was_message_by_human": true,
  "referral": {
    "source_type": "ad",
    "source_id": "52540693396957",
    "source_url": "https://www.instagram.com/p/DZiVBz7gAF9/",
    "headline": "Expo Nissan",
    "body": "Aprovechá la EXPONISSAN y llevate tu nuevo Nissan Kicks Play Sense MT con condiciones que juegan a tu favor.",
    "media_type": "image",
    "image_url": "https://scontent.xx.fbcdn.net/v/t45.1600-4/example.jpg",
    "ctwa_clid": "AfhN-JKvx8HeFTmfB-Tu11zktQRJ-MNdMV1mwvDNxHnpYrGl-jVf3OEFhLva_MP41zYRe5ErUteWFn3v4gkkjzfIEVr9J_u8GAo3-o6DqShykM4Zsl14FcU5MyThsCoQ"
  }
}
```

`video_url`, `thumbnail_url`, and `welcome_message` are documented LIVE keys; they may be absent from a given sample when Meta did not send them.

***

## Delivery paths

| Destination | How `referral` arrives |
| - | - |
| Custom HTTPS webhook | Whatsable POSTs the payload including `referral` when present |
| n8n / Make / Zapier triggers | Same object on the trigger; filter when `referral` exists |
| Agent Skills `create-webhook.js --incoming` | Creates a webhook that receives incoming (and `--outgoing` if set) — payload reference stays on Message webhooks |

Field companions when mapping in each tool: [Zapier fields](/guides/notifyer-system/zapier-fields) · [Make fields](/guides/notifyer-system/make-fields) · [n8n fields](/guides/notifyer-system/n8n-fields).

<Tip>
  In n8n, Make, or Zapier, add a filter or router: only treat the event as ad-attributed when `referral` exists (or `referral.source_type` is `"ad"`). Map `referral.headline`, `referral.source_url`, and `referral.source_id` into your CRM so reporting matches Meta Ads Manager.
</Tip>

***

## Limits and what this does NOT do

<Warning>
  **First inbound only (typical).** Do not expect `referral` on every message in the thread. Store `ctwa_clid` and `source_id` immediately.
</Warning>

<Warning>
  **Status ads may omit `ctwa_clid`.** Other referral fields can still be present. Organic posts use `source_type: "post"`.
</Warning>

* **No invent nested `welcome_message` children** — object only until verified.
* **No invent inbox creative UI schema** beyond webhook forwarding of `referral.*`.
* **No Facebook Lead Ads form** payload as CTWA — different Meta product.
* **No legacy Bot / legacy `/guides/webhooks`** envelope as the CTWA shape — use [Message webhooks](/guides/notifyer-system/api/incoming-message).
* **No pixel / CAPI claims beyond** documented use of `ctwa_clid` with Meta Conversions API for Business Messaging.
* Typing-indicator dots and a native drip builder are out of scope for this page.

***

## Related features and next steps

<CardGroup>
  <Card title="Message webhooks" icon="webhook" href="/guides/notifyer-system/api/incoming-message">
    Full inbound/outbound payload, signatures, and CTWA section
  </Card>

  <Card title="Zapier fields" icon="bolt" href="/guides/notifyer-system/zapier-fields">
    Trigger output dictionary including nested `referral`
  </Card>

  <Card title="Make fields" icon="diagram-project" href="/guides/notifyer-system/make-fields">
    Module field dictionary for Make
  </Card>

  <Card title="n8n fields" icon="gear" href="/guides/notifyer-system/n8n-fields">
    Node field dictionary for n8n
  </Card>
</CardGroup>

Also: [n8n overview](/guides/notifyer-system/n8n-overview) · [Make overview](/guides/notifyer-system/make-overview) · [Zapier overview](/guides/notifyer-system/zapier-overview) · [Click-to-WhatsApp ads (anchor)](/guides/notifyer-system/api/incoming-message#click-to-whatsapp-ads).

***

## FAQ

### Do Whatsable webhooks include Click-to-WhatsApp ad details?

Yes. When the contact's message comes from a Click-to-WhatsApp ad (or organic post with referral), the payload includes a `referral` object (`source_id`, `source_url`, `source_type`, `headline`, `body`, `media_type`, creative URLs, and usually `ctwa_clid`). Full field list is on this page; parent payload reference: [Message webhooks](/guides/notifyer-system/api/incoming-message#click-to-whatsapp-ads).

### Why is `referral` missing on later messages?

Meta / Whatsable typically attach `referral` only on the **first** inbound after the tap. Persist `ctwa_clid` and `source_id` keyed on `phone_number` when you first see them.

### Where do I look in a Cloud API–shaped delivery?

Use `entry[].changes[].value.messages[].referral`. On the flattened Whatsable webhook body, look for top-level `referral`.

### Can I send `ctwa_clid` to Meta Conversions API?

Yes — that is the documented purpose of `ctwa_clid` (Business Messaging / WhatsApp). Status placements may omit the click ID; do not invent other pixel fields on this webhook.


# Get Templates
Source: https://docs.whatsable.app/guides/notifyer-system/api/get-templates

Retrieve and manage your WhatsApp message templates

<Tip>
  Templates are pre-approved message formats that ensure your WhatsApp communications comply with WhatsApp Business policies while maintaining consistent messaging with your audience.
</Tip>

WhatsApp templates are essential for business messaging, enabling you to send structured communications to customers while complying with WhatsApp's policies. This guide covers how to retrieve your templates using our API.

## Overview

Templates serve as the foundation for all non-session messages on WhatsApp Business. Each template:

* Must be pre-approved by WhatsApp before use
* Belongs to a specific category (Marketing, Utility, Authentication)
* Can include variables that personalize messages for each recipient
* Supports multiple languages and formats (text, media, interactive components)

<Card title="Try it in the API Reference" icon="arrow-right" href="https://docs.whatsable.app/api-reference/notifier-system/templates/get-templates">
  Experiment with the Get Templates API and view responses in real-time
</Card>

## Get Templates

Retrieve all WhatsApp templates associated with your account, including approval status, variables, and other key properties.

### Endpoint

```
GET https://api.insightssystem.com/api:AFRA_QCy/get_templates
```

### Authentication

<Warning>
  All API requests require authentication using your API key. Never share your API keys in client-side code.
</Warning>

Include your API key in all requests using Bearer authentication:

<CodeGroup>
  ```bash theme={null}
  Authorization: Bearer YOUR_API_KEY
  ```

  ```javascript theme={null}
  headers: {
    'Authorization': 'Bearer YOUR_API_KEY',
    'Content-Type': 'application/json'
  }
  ```
</CodeGroup>

### Response

The API returns an array of template objects, each containing detailed information about your WhatsApp templates.

<ResponseField name="id" type="integer">
  Unique identifier for the template
</ResponseField>

<ResponseField name="user_id" type="string">
  UUID of the account that owns the template
</ResponseField>

<ResponseField name="name" type="string">
  Unique name identifier of the template
</ResponseField>

<ResponseField name="category" type="string">
  <Expandable title="category options">
    <ResponseField name="MARKETING" type="string">
      Promotional content and offers
    </ResponseField>

    <ResponseField name="UTILITY" type="string">
      Transactional messages like order confirmations
    </ResponseField>

    <ResponseField name="AUTHENTICATION" type="string">
      Security codes and verification messages
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="type" type="string">
  Format type of the template (text, media, etc.)
</ResponseField>

<ResponseField name="language" type="string">
  Language code (e.g., "en", "en\_US")
</ResponseField>

<ResponseField name="status" type="string">
  <Expandable title="status options">
    <ResponseField name="APPROVED" type="string">
      Template is ready to use
    </ResponseField>

    <ResponseField name="PENDING" type="string">
      Template is awaiting WhatsApp review
    </ResponseField>

    <ResponseField name="REJECTED" type="string">
      Template was rejected by WhatsApp
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="variable_counts" type="integer">
  Number of variable placeholders in the template
</ResponseField>

<ResponseField name="template_formate" type="string">
  Format string showing variable placement (e.g., "\[b:7]")
</ResponseField>

<ResponseField name="template_id" type="string">
  UUID of the template in our system
</ResponseField>

### Example Request

<CodeGroup>
  ```bash cURL theme={null}
  curl -X GET \
    https://api.insightssystem.com/api:AFRA_QCy/get_templates \
    -H 'Content-Type: application/json' \
    -H 'Authorization: Bearer YOUR_API_KEY'
  ```

  ```javascript Node.js theme={null}
  const axios = require('axios');

  async function getTemplates() {
    try {
      const response = await axios.get(
        'https://api.insightssystem.com/api:AFRA_QCy/get_templates',
        {
          headers: {
            'Content-Type': 'application/json',
            'Authorization': 'Bearer YOUR_API_KEY'
          }
        }
      );
      console.log(response.data);
      return response.data;
    } catch (error) {
      console.error('Error fetching templates:', error);
    }
  }

  getTemplates();
  ```

  ```python Python theme={null}
  import requests

  url = "https://api.insightssystem.com/api:AFRA_QCy/get_templates"

  headers = {
      "Content-Type": "application/json",
      "Authorization": "Bearer YOUR_API_KEY"
  }

  response = requests.get(url, headers=headers)
  print(response.json())
  ```
</CodeGroup>

### Example Response

<CodeGroup>
  ```json Response theme={null}
  [
    {
      "id": 300,
      "user_id": "a9d7c221-62d2-43b5-810a-8a1a71c7820c",
      "name": "exclusive_offer_alert",
      "category": "MARKETING",
      "type": "text",
      "language": "en",
      "status": "APPROVED",
      "variable_counts": 7,
      "template_formate": "[b:7]",
      "template_id": "6f6e4113-cc8a-4fbe-b98d-2c631d299c6b"
    },
    {
      "id": 150,
      "user_id": "a9d7c221-62d2-43b5-810a-8a1a71c7820c",
      "name": "general_communication_message",
      "category": "UTILITY",
      "type": "text",
      "language": "en",
      "status": "REJECTED",
      "variable_counts": 0,
      "template_formate": "[]",
      "template_id": "75521873-72cd-4c33-9072-c8b901d6f687"
    }
  ]
  ```
</CodeGroup>

## Response Codes

<AccordionGroup>
  <Accordion title="200: Success">
    Your request was successful and the templates have been returned.
  </Accordion>

  <Accordion title="401: Unauthorized">
    Authentication failed. Check that you're using a valid API key.

    ```json theme={null}
    {
      "error": {
        "code": "unauthorized",
        "message": "Invalid API key provided"
      }
    }
    ```
  </Accordion>

  <Accordion title="403: Forbidden">
    Your account doesn't have permission to access templates.
  </Accordion>

  <Accordion title="429: Too Many Requests">
    You've exceeded the rate limit. Implement exponential backoff in your requests.
  </Accordion>

  <Accordion title="500: Server Error">
    Something went wrong on our end. Please contact support if the issue persists.

    ```json theme={null}
    {
      "error": {
        "code": "server_error",
        "message": "An internal server error occurred"
      }
    }
    ```
  </Accordion>
</AccordionGroup>

## Working with Templates

<Steps>
  <Step title="Retrieve templates">
    Use the Get Templates API to fetch all templates associated with your account.
  </Step>

  <Step title="Check template status">
    Verify that your templates are in the "APPROVED" status before using them.
  </Step>

  <Step title="Identify variable placeholders">
    Note the `variable_counts` and `template_formate` to understand how many variables need to be provided when sending a message.
  </Step>

  <Step title="Send messages">
    Use the template ID and required variables to send messages via the [Send Template API](/api-reference/notifier-system/send-template).
  </Step>
</Steps>

## Template Best Practices

<CardGroup>
  <Card title="Variable Management" icon="wand-magic-sparkles">
    Keep track of which variables correspond to which placeholders in your template. Consider creating a mapping in your application.
  </Card>

  <Card title="Template Versioning" icon="code-branch">
    Templates can't be edited after submission, but you can create new versions. Use a versioning system in your template names (e.g., welcome\_v2).
  </Card>

  <Card title="Status Monitoring" icon="gauge">
    Regularly check the status of your templates, as WhatsApp can change approval statuses based on user feedback.
  </Card>

  <Card title="Language Support" icon="language">
    Create templates in multiple languages to communicate with your global audience in their preferred language.
  </Card>
</CardGroup>

## FAQs

<AccordionGroup>
  <Accordion title="How long does template approval take?">
    WhatsApp typically reviews templates within 24-48 hours, but this can vary depending on template content and current review volumes.
  </Accordion>

  <Accordion title="Why was my template rejected?">
    Templates may be rejected if they violate WhatsApp's Business Policy, contain prohibited content, or don't match the selected category. Check our [Template Guidelines](/guides/whatsapp/template-guidelines) for more information.
  </Accordion>

  <Accordion title="Can I edit an existing template?">
    No, once submitted, templates cannot be modified. You'll need to create a new template with your desired changes.
  </Accordion>

  <Accordion title="What are the template character limits?">
    Text-only templates have a limit of 1,024 characters. Templates with media have different limits based on the header type.
  </Accordion>
</AccordionGroup>

<Card title="Need help?" icon="headset" href="mailto:team@whatsable.app">
  Our support team is available 24/7 to assist with template issues, API integration, or any other questions.
</Card>


# Message webhooks
Source: https://docs.whatsable.app/guides/notifyer-system/api/incoming-message

Receive incoming and outgoing WhatsApp messages via webhooks — including replies typed in the WhatsApp Business app and Click-to-WhatsApp ad referral data (creative, platform, ctwa_clid).

<Tip>
  Message webhooks POST a JSON payload to your HTTPS endpoint whenever a WhatsApp message is **received or sent** on your connected number — including messages typed by hand in the WhatsApp Business app.
</Tip>

<Info>
  **Meta WhatsApp Coexistence is supported on Notifyer System.** You do **not** need to delete the WhatsApp Business app or stop using the number on your phone. After Embedded Signup, the same number works in the WhatsApp Business app, the Notifyer chat inbox, and automations (Make, Zapier, n8n, API, and webhooks) at the same time.
</Info>

Configure an endpoint once, then use it from n8n, Make, Zapier, or your own server. This page is the full payload reference.

## Overview

Webhooks are HTTP callbacks that Notifyer sends to your server when a message event occurs. They cover:

* **Incoming messages** — a contact writes to your business
* **Outgoing messages** — your business sends a message, including:
  * Hand-typed replies in the **WhatsApp Business app** on a phone
  * Messages sent from the **Notifyer chat inbox** (with the teammate's name)
  * Messages sent by **Make, Zapier, n8n, the API, or a bot**
* **Click-to-WhatsApp ads** — when the inbound message came from a Facebook, Instagram, or WhatsApp Status ad, a `referral` object identifies the creative, platform, and click (`ctwa_clid`)

Use this to trigger automations, sync CRMs, attribute ad leads, and log full conversation history — not only inbound chat.

## Webhook Configuration

### Managing Endpoints

<Steps>
  <Step title="Access Webhook Settings">
    Navigate to the Developer section in your dashboard sidebar to manage webhook configurations.
  </Step>

  <Step title="Configure Endpoint">
    Add a new webhook URL. Enable **incoming**, **outgoing**, or both depending on which events your endpoint should receive.
  </Step>
</Steps>

### Endpoint Requirements

<Warning>
  All webhook endpoints must be publicly accessible via HTTPS and configured to accept POST requests with JSON payloads. HTTP endpoints are not supported in production environments.
</Warning>

Your webhook endpoint must:

1. Accept HTTP POST requests
2. Process JSON payloads
3. Return a 2xx status code within 10 seconds
4. Implement idempotency handling (see best practices below)

## Incoming and outgoing WhatsApp messages

Notifyer delivers **both incoming and outgoing** messages to your webhook or automation trigger — including messages typed by hand in the **WhatsApp Business app** on your phone.

This is possible because Notifyer supports [Meta WhatsApp Coexistence](/guides/notifyer-system/embedding-process#whatsapp-coexistence). You keep using WhatsApp Business on your phone; those hand-typed replies still reach an external webhook and can start an automation. They are not limited to the Notifyer web inbox.

<Frame>
  <iframe title="Trigger n8n workflows with WhatsApp messages" />
</Frame>

The payload is the same whether you use [n8n](/guides/notifyer-system/n8n-overview), [Make](/guides/notifyer-system/make-overview), [Zapier](/guides/notifyer-system/zapier-overview), or a [custom webhook](/guides/notifyer-system/api/incoming-message). [Watch the walkthrough on YouTube](https://www.youtube.com/watch?v=UfW-KwS4gBI).

### Direction, sending system, and team member

Use these three fields to tell *what happened* and *who sent it*:

<ResponseField name="incoming_message" type="boolean">
  `true` when a contact sent a message **to** your business. `false` when your business sent a message **to** the contact (outgoing). Filter on this field to run logic only for one direction.
</ResponseField>

<ResponseField name="send_by" type="string">
  Which system or person sent an **outgoing** message:

  | `send_by` value | Meaning |
  | - | - |
  | `WhatsApp App` | Typed by hand in the WhatsApp Business app on a phone |
  | A team member's name (for example `Axel Meta`) | Sent from the Notifyer chat inbox by that logged-in user |
  | An automation or app name (Make, Zapier, n8n, API, bot) | Sent by that integration or bot |

  Empty or omitted on incoming messages.
</ResponseField>

<ResponseField name="was_message_by_human" type="boolean">
  `true` when a person sent the message (WhatsApp Business app or Notifyer chat inbox). `false` when a bot or automation sent it. Combine with `send_by` to see both *whether* a human sent it and *which teammate or system* did.
</ResponseField>

### Example payload: message typed on the phone

This is the JSON Notifyer POSTs when someone types a reply in the WhatsApp Business app. `incoming_message` is `false`, `send_by` is `"WhatsApp App"`, and `was_message_by_human` is `true`.

```json theme={null}
{
  "last_messages": "[{\"type\":\"bot\",\"content\":\"Hello n8n\",\"timestamp\":\"2026-08-15T12:24:47.000Z\",\"content_type\":\"text\"},{\"type\":\"user\",\"content\":\"hi\",\"timestamp\":\"2026-08-12T12:27:42.746Z\",\"content_type\":\"text\"}]",
  "conversation_paragraph": "Bot (12:24:47 PM): Hello n8n ; User (12:27:42 PM): hi",
  "phone_number": 14155552671,
  "recipient_name": "Alex Martinez",
  "user_id": "158c59e1-ea85-4d0b-b70c-65328ba67a8e",
  "last_message_of_user": "hi",
  "last_message_of_bot": "Hello n8n",
  "message_type": "text",
  "user_last_message_time": 1786722580,
  "bot_last_message_time": 1786797014,
  "attachment_url": null,
  "note": "email: alex\nName: Alex",
  "note_automation": "email: alex\nName: Alex",
  "labels": "n8n, webhook-test",
  "incoming_message": false,
  "send_by": "WhatsApp App",
  "was_message_by_human": true
}
```

<Note>
  `last_message_of_bot` is the last message **your business** sent — whether a human typed it in the WhatsApp Business app or the Notifyer inbox, or a bot/automation sent it. `last_messages` is a JSON **string** of the last \~20 messages (parse it before iterating). `phone_number` may arrive as a number rather than a string.
</Note>

When the same person sends from the Notifyer chat inbox instead of the phone app, the payload is identical except:

```json theme={null}
{
  "incoming_message": false,
  "send_by": "Axel Meta",
  "was_message_by_human": true
}
```

## Webhook payload

When a message is received or sent on your connected number, Notifyer sends a `POST` request to your endpoint with a JSON body.

### Sample payloads

<CodeGroup>
  ```json Incoming Text Message theme={null}
  {
    "last_messages": [
      {
        "type": "user",
        "content": "Thank you for the quick response. Can you provide more details about your premium service plans?",
        "timestamp": "2025-06-09T22:08:11.990Z",
        "content_type": "text"
      },
      {
        "type": "bot",
        "content": "I'd be happy to help you explore our premium service options. Let me connect you with a specialist who can provide detailed information.",
        "timestamp": "2025-06-09T21:45:30.417Z",
        "content_type": "text"
      }
    ],
    "conversation_paragraph": "User (10:08:11 PM): Thank you for the quick response. Can you provide more details about your premium service plans? ; Bot (9:45:30 PM): I'd be happy to help you explore our premium service options. Let me connect you with a specialist who can provide detailed information.",
    "phone_number": "14155552671",
    "recipient_name": "Sarah Johnson",
    "user_id": "9232fcef-a570-4a2c-b46b-6cab53aec304",
    "last_message_of_user": "Thank you for the quick response. Can you provide more details about your premium service plans?",
    "last_message_of_bot": "I'd be happy to help you explore our premium service options. Let me connect you with a specialist who can provide detailed information.",
    "message_type": "text",
    "user_last_message_time": 1749506891,
    "bot_last_message_time": 1749504330,
    "attachment_url": null,
    "note": "",
    "note_automation": "",
    "labels": "sales, premium-inquiry",
    "incoming_message": true,
    "send_by": "",
    "was_message_by_human": true
  }
  ```

  ```json Incoming Media Message theme={null}
  {
    "last_messages": [
      {
        "type": "user",
        "content": "",
        "timestamp": "2025-06-09T14:05:12.000Z",
        "content_type": "document",
        "media_url": "https://api.insightssystem.com/vault/LSMumRx1/VR-1aHOci6nP28eHWHJH7JauJkc/Ew7R9w../contract_proposal_v2.pdf"
      },
      {
        "type": "bot",
        "content": "Please upload the signed contract document when ready, and I'll process it immediately.",
        "timestamp": "2025-06-09T14:03:20.000Z",
        "content_type": "text"
      }
    ],
    "conversation_paragraph": "User (2:05:12 PM): [Document] ; Bot (2:03:20 PM): Please upload the signed contract document when ready, and I'll process it immediately.",
    "phone_number": "14155552671",
    "recipient_name": "Sarah Johnson",
    "user_id": "9232fcef-a570-4a2c-b46b-6cab53aec304",
    "last_message_of_user": "",
    "last_message_of_bot": "Please upload the signed contract document when ready, and I'll process it immediately.",
    "message_type": "document",
    "user_last_message_time": 1749472312,
    "bot_last_message_time": 1749472200,
    "attachment_url": "https://api.insightssystem.com/vault/LSMumRx1/VR-1aHOci6nP28eHWHJH7JauJkc/Ew7R9w../contract_proposal_v2.pdf",
    "note": "",
    "note_automation": "",
    "labels": "contracts, document-processing",
    "incoming_message": true,
    "send_by": "",
    "was_message_by_human": true
  }
  ```

  ```json Outgoing — typed in WhatsApp Business app theme={null}
  {
    "last_messages": "[{\"type\":\"bot\",\"content\":\"Hello n8n\",\"timestamp\":\"2026-08-15T12:24:47.000Z\",\"content_type\":\"text\"},{\"type\":\"user\",\"content\":\"hi\",\"timestamp\":\"2026-08-12T12:27:42.746Z\",\"content_type\":\"text\"}]",
    "conversation_paragraph": "Bot (12:24:47 PM): Hello n8n ; User (12:27:42 PM): hi",
    "phone_number": 14155552671,
    "recipient_name": "Alex Martinez",
    "user_id": "158c59e1-ea85-4d0b-b70c-65328ba67a8e",
    "last_message_of_user": "hi",
    "last_message_of_bot": "Hello n8n",
    "message_type": "text",
    "user_last_message_time": 1786722580,
    "bot_last_message_time": 1786797014,
    "attachment_url": null,
    "note": "email: alex\nName: Alex",
    "note_automation": "email: alex\nName: Alex",
    "labels": "n8n, webhook-test",
    "incoming_message": false,
    "send_by": "WhatsApp App",
    "was_message_by_human": true
  }
  ```

  ```json Outgoing — teammate in Notifyer chat theme={null}
  {
    "last_messages": "[{\"type\":\"bot\",\"content\":\"Hi, I can help with that.\",\"timestamp\":\"2026-08-15T14:02:10.000Z\",\"content_type\":\"text\"}]",
    "conversation_paragraph": "Bot (2:02:10 PM): Hi, I can help with that.",
    "phone_number": 14155552671,
    "recipient_name": "Alex Martinez",
    "user_id": "158c59e1-ea85-4d0b-b70c-65328ba67a8e",
    "last_message_of_user": "Can you help with scheduling?",
    "last_message_of_bot": "Hi, I can help with that.",
    "message_type": "text",
    "user_last_message_time": 1786722580,
    "bot_last_message_time": 1786802530,
    "attachment_url": null,
    "note": "",
    "note_automation": "",
    "labels": "support",
    "incoming_message": false,
    "send_by": "Axel Meta",
    "was_message_by_human": true
  }
  ```

  ```json Incoming — Click-to-WhatsApp ad theme={null}
  {
    "last_messages": [
      {
        "type": "user",
        "content": "Quiero información",
        "timestamp": "2026-08-15T18:18:36.000Z",
        "content_type": "text"
      }
    ],
    "conversation_paragraph": "User (6:18:36 PM): Quiero información",
    "phone_number": "50655550100",
    "recipient_name": "Maria Lopez",
    "user_id": "9232fcef-a570-4a2c-b46b-6cab53aec304",
    "last_message_of_user": "Quiero información",
    "last_message_of_bot": "",
    "message_type": "text",
    "user_last_message_time": 1781734716,
    "bot_last_message_time": 0,
    "attachment_url": null,
    "note": "",
    "note_automation": "",
    "labels": "",
    "incoming_message": true,
    "send_by": "",
    "was_message_by_human": true,
    "referral": {
      "source_type": "ad",
      "source_id": "52540693396957",
      "source_url": "https://www.instagram.com/p/DZiVBz7gAF9/",
      "headline": "Expo Nissan",
      "body": "Aprovechá la EXPONISSAN y llevate tu nuevo Nissan Kicks Play Sense MT con condiciones que juegan a tu favor.",
      "media_type": "image",
      "image_url": "https://scontent.xx.fbcdn.net/v/t45.1600-4/example.jpg",
      "ctwa_clid": "AfhN-JKvx8HeFTmfB-Tu11zktQRJ-MNdMV1mwvDNxHnpYrGl-jVf3OEFhLva_MP41zYRe5ErUteWFn3v4gkkjzfIEVr9J_u8GAo3-o6DqShykM4Zsl14FcU5MyThsCoQ"
    }
  }
  ```
</CodeGroup>

### Payload Fields

<ResponseField name="last_messages" type="string | array">
  Recent messages in the conversation (about the last 20). On webhook deliveries this is typically a **JSON string** — parse it before iterating. Each item includes `type` (`user` or `bot`), `content`, `timestamp`, and `content_type`. Includes messages from the WhatsApp Business app, the Notifyer inbox, automations, and templates.

  <Expandable title="last_messages array">
    <ResponseField name="type" type="string">
      Sender type ("user" or "bot")
    </ResponseField>

    <ResponseField name="content" type="string">
      Message content (empty for media messages)
    </ResponseField>

    <ResponseField name="timestamp" type="string">
      ISO 8601 timestamp when the message was sent
    </ResponseField>

    <ResponseField name="content_type" type="string">
      Type of content (text, image, audio, video, document, location)
    </ResponseField>

    <ResponseField name="media_url" type="string">
      URL to media file if applicable (valid for 24 hours)
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="conversation_paragraph" type="string">
  Human-readable summary of the recent conversation
</ResponseField>

<ResponseField name="phone_number" type="string | number">
  WhatsApp number of the contact in this conversation (digits, often without `+`). On outgoing events this is the person your business messaged. May arrive as a number or a string.
</ResponseField>

<ResponseField name="recipient_name" type="string">
  The name of the recipient if available
</ResponseField>

<ResponseField name="user_id" type="string">
  Unique identifier for the user in your system
</ResponseField>

<ResponseField name="last_message_of_user" type="string">
  The last message sent by the user
</ResponseField>

<ResponseField name="last_message_of_bot" type="string">
  The last message your business sent — whether a human typed it in the WhatsApp Business app or Notifyer inbox, or a bot/automation sent it
</ResponseField>

<ResponseField name="message_type" type="string">
  The type of the latest message (text, image, audio, video, document, location)
</ResponseField>

<ResponseField name="user_last_message_time" type="integer">
  Unix timestamp of the user's last message
</ResponseField>

<ResponseField name="bot_last_message_time" type="integer">
  Unix timestamp of your system's last message
</ResponseField>

<ResponseField name="attachment_url" type="string">
  URL to media file if the latest message contains media (null for text messages)
</ResponseField>

<ResponseField name="note" type="string">
  Custom note field for additional context
</ResponseField>

<ResponseField name="note_automation" type="string">
  Automation-related notes
</ResponseField>

<ResponseField name="labels" type="string">
  Comma-separated labels for categorizing the conversation
</ResponseField>

<ResponseField name="incoming_message" type="boolean">
  `true` when the contact sent this message to your business. `false` when your business sent it (outgoing). Outgoing events include messages typed in the WhatsApp Business app, sent from the Notifyer chat inbox, or sent by Make, Zapier, n8n, the API, or a bot.
</ResponseField>

<ResponseField name="send_by" type="string">
  Which system or person sent an outgoing message. `"WhatsApp App"` when typed in the WhatsApp Business app; the logged-in teammate's name when sent from the Notifyer chat inbox; the automation or app name for Make, Zapier, n8n, API, or a bot. Empty on incoming messages.
</ResponseField>

<ResponseField name="was_message_by_human" type="boolean">
  `true` when a person sent the message (WhatsApp Business app or Notifyer chat inbox). `false` when a bot or automation sent it.
</ResponseField>

<ResponseField name="referral" type="object">
  Present on **incoming** events that originated from a Click-to-WhatsApp ad or post. Omitted on ordinary chats and on most follow-up messages after the first ad-attributed inbound. See [Click-to-WhatsApp ads](#click-to-whatsapp-ads).

  <Expandable title="referral object">
    <ResponseField name="source_type" type="string">
      `"ad"` or `"post"`
    </ResponseField>

    <ResponseField name="source_id" type="string">
      Meta ad or post ID
    </ResponseField>

    <ResponseField name="source_url" type="string">
      URL of the ad or post (platform is in the host)
    </ResponseField>

    <ResponseField name="headline" type="string">
      Ad or post headline
    </ResponseField>

    <ResponseField name="body" type="string">
      Ad or post body copy
    </ResponseField>

    <ResponseField name="media_type" type="string">
      `"image"` or `"video"`
    </ResponseField>

    <ResponseField name="image_url" type="string">
      Image creative URL
    </ResponseField>

    <ResponseField name="video_url" type="string">
      Video creative URL
    </ResponseField>

    <ResponseField name="thumbnail_url" type="string">
      Video thumbnail URL
    </ResponseField>

    <ResponseField name="ctwa_clid" type="string">
      Click ID for Meta Conversions API attribution
    </ResponseField>
  </Expandable>
</ResponseField>

## Click-to-WhatsApp ads

When someone taps **Send message** on a Click-to-WhatsApp ad (Facebook, Instagram, or WhatsApp Status) and writes to your number, Meta attaches a `referral` object to that inbound message. Notifyer passes it through to your [custom webhook](#webhook-payload) and to [n8n](/guides/notifyer-system/n8n-overview), [Make](/guides/notifyer-system/make-overview), and [Zapier](/guides/notifyer-system/zapier-overview) triggers.

Use it to optimize campaigns: see **which creative**, **which platform**, and **which ad** produced the lead, then label the conversation, route it to the right team, or send `ctwa_clid` to Meta's Conversions API.

<Note>
  `referral` is typically present only on the **first inbound message** after the ad click. Later messages in the same chat usually omit it. Persist `ctwa_clid` and `source_id` (keyed on the contact's phone) as soon as they arrive.
</Note>

<Info>
  WhatsApp Status ad placements may omit `ctwa_clid`. Organic posts use `source_type: "post"` instead of `"ad"`.
</Info>

### What each field is for

| Goal | Fields |
| - | - |
| Group leads by campaign or creative | `source_id`, `headline` |
| See Facebook vs Instagram vs other | `source_url` (host is `instagram.com`, `facebook.com`, `fb.me`, …) |
| Show agents the ad the lead saw | `headline`, `body`, `image_url` / `video_url`, `media_type` |
| Send conversions back to Meta | `ctwa_clid` |

### Referral object

Look for `referral` as a top-level field on the Notifyer payload, or at `entry[].changes[].value.messages[].referral` if the delivery includes the Cloud API envelope.

<ResponseField name="source_type" type="string">
  `"ad"` when the lead tapped an ad. `"post"` when they came from an organic post.
</ResponseField>

<ResponseField name="source_id" type="string">
  Meta ID of the ad or post. Use this to group and compare creatives.
</ResponseField>

<ResponseField name="source_url" type="string">
  URL of the ad or post the contact tapped. The host tells you the platform (for example Instagram permalink vs Facebook/ad link).
</ResponseField>

<ResponseField name="headline" type="string">
  Headline shown on the ad or post.
</ResponseField>

<ResponseField name="body" type="string">
  Body copy of the ad or post. May include emoji shortcodes such as `:fire:`.
</ResponseField>

<ResponseField name="media_type" type="string">
  Creative type: `"image"` or `"video"`.
</ResponseField>

<ResponseField name="image_url" type="string">
  URL of the image creative when `media_type` is `"image"`. These URLs can expire — copy any asset you need to keep.
</ResponseField>

<ResponseField name="video_url" type="string">
  URL of the video creative when `media_type` is `"video"`.
</ResponseField>

<ResponseField name="thumbnail_url" type="string">
  Thumbnail URL for video creatives.
</ResponseField>

<ResponseField name="ctwa_clid" type="string">
  Click-to-WhatsApp click ID. Pass this to Meta Conversions API for Business Messaging (`action_source: "business_messaging"`, `messaging_channel: "whatsapp"`) so purchases and qualified leads attribute back to the ad.
</ResponseField>

<ResponseField name="welcome_message" type="object">
  Optional. Welcome message configured on the ad, when Meta includes it.
</ResponseField>

### Cloud API envelope example

This is the Meta WhatsApp Business Account shape. The attribution lives on `messages[].referral`. Contact identifiers in this example are anonymized; the referral fields match a real Instagram Click-to-WhatsApp ad.

```json theme={null}
{
  "object": "whatsapp_business_account",
  "entry": [
    {
      "id": "1824807628200899",
      "changes": [
        {
          "field": "messages",
          "value": {
            "messaging_product": "whatsapp",
            "metadata": {
              "display_phone_number": "50660039931",
              "phone_number_id": "1070485179471457"
            },
            "contacts": [
              {
                "profile": {
                  "name": "Maria Lopez"
                },
                "wa_id": "50655550100",
                "user_id": "CR.10162597228035267"
              }
            ],
            "messages": [
              {
                "from": "50655550100",
                "id": "wamid.HBgLNTA2NTU1NTAxMDAVAgASGBQzEXAMPLE",
                "timestamp": "1781734716",
                "type": "text",
                "text": {
                  "body": "Quiero información"
                },
                "from_user_id": "CR.10162597228035267",
                "referral": {
                  "source_type": "ad",
                  "source_id": "52540693396957",
                  "source_url": "https://www.instagram.com/p/DZiVBz7gAF9/",
                  "headline": "Expo Nissan",
                  "body": ":soccer::fire: ¡Llegó el momento de hacer la mejor jugada! :fire:Aprovechá la EXPONISSAN y llevate tu nuevo Nissan Kicks Play Sense MT con condiciones que juegan a tu favor:\n\n:car: Precio de fábrica: $23,900\n:moneybag: Ahorro de $3,000\n:package: Entrega inmediata\n:zap: Financiamiento especial disponible\n\n:hourglass_flowing_sand: Promoción por tiempo limitado.\n\nReservá y cotizá a través de nuestro punto de venta digital:\n:point_right: www.nissancr.com/servicios/solicitar-cotizacion.html\nO contactános por WhatsApp:\n:point_right: https://wa.me/50660039931",
                  "media_type": "image",
                  "image_url": "https://scontent.xx.fbcdn.net/v/t45.1600-4/example.jpg",
                  "ctwa_clid": "AfhN-JKvx8HeFTmfB-Tu11zktQRJ-MNdMV1mwvDNxHnpYrGl-jVf3OEFhLva_MP41zYRe5ErUteWFn3v4gkkjzfIEVr9J_u8GAo3-o6DqShykM4Zsl14FcU5MyThsCoQ"
                }
              }
            ]
          }
        }
      ]
    }
  ]
}
```

<Tip>
  In n8n, Make, or Zapier, add a filter or router: only treat the event as ad-attributed when `referral` exists (or `referral.source_type` is `"ad"`). Map `referral.headline`, `referral.source_url`, and `referral.source_id` into your CRM so reporting matches Meta Ads Manager.
</Tip>

## Webhook Management API

You can programmatically manage your webhook endpoints using our API.

### Create Webhook Endpoint

`POST https://api.insightssystem.com/api:qh9OQ3OW/webhook/dev/create`

Register a new webhook endpoint to receive incoming message notifications. Send a valid **Bearer** token (same credential used for the dashboard).

#### Request Body

<ParamField type="string">
  Full HTTPS URL of your endpoint.
</ParamField>

<ParamField type="boolean">
  Whether the webhook is enabled.
</ParamField>

<ParamField type="boolean">
  Incoming message trigger on/off. When `true`, your endpoint receives messages contacts send to your business.
</ParamField>

<ParamField type="boolean">
  Outgoing message trigger on/off. When `true`, your endpoint also receives messages your business sends — including hand-typed replies in the WhatsApp Business app, Notifyer chat inbox messages, and messages sent by Make, Zapier, n8n, the API, or a bot. Set this to `true` if an automation must react to messages typed on the phone.
</ParamField>

<ParamField type="boolean">
  Schedule activity trigger on/off. When enabled, your bot can send multiple sequential messages with natural delays between them — useful for simulating human-like conversation flow.
</ParamField>

**How to enable in the dashboard**

Navigate to **Incoming Webhooks**, click the settings icon next to your webhook, then enable **Schedule Activity**. A dropdown will appear where you can select your preferred delay duration between messages.

<Frame>
  <img alt="How to enable Schedule Activity and set delay duration" />
</Frame>

**Example workflow**

When a user sends an incoming message, you can respond with a sequence of messages each sent after a specified delay:

```json theme={null}
{
  "messages": [
    {
      "text": "Great! Let me check available slots for you...",
      "delay": 0
    },
    {
      "text": "I can see openings on Monday and Wednesday.",
      "delay": 2000
    },
    {
      "text": "Which day works better for you?",
      "delay": 3500
    }
  ]
}
```

Set `waiting_duration` to the maximum delay window you need. When `schedule_activity` is `false`, set `waiting_duration` to `0`.

<ParamField type="number">
  How long (in **seconds**) to wait for schedule activity when `schedule_activity` is `true`. Set to `0` when schedule activity is off.

  Dashboard presets: `15`, `30`, `60`, `1800`, `3600`, `18000`, `36000`, `86400`, `172800`, `259200`, `432000`, `604800`, `1209600`, `2592000`, `5184000` (15 seconds → 2 months). Prefer these values if mirroring the app UI.
</ParamField>

<ParamField type="boolean">
  If `true`, enables request signing. The server returns a `signature_secret` **once** in the response — copy and store it immediately, as it will not be shown again.
</ParamField>

<Frame>
  <img alt="Webhook signature toggle in the Add Endpoint dialog" />
</Frame>

<CodeGroup>
  ```bash cURL theme={null}
  curl -X POST \
    https://api.insightssystem.com/api:qh9OQ3OW/webhook/dev/create \
    -H 'Content-Type: application/json' \
    -H 'Authorization: Bearer YOUR_TOKEN' \
    -d '{
      "webhooks": "https://your-domain.com/api/webhooks/whatsapp",
      "status": true,
      "incoming": true,
      "outgoing": true,
      "schedule_activity": false,
      "waiting_duration": 0,
      "active_signature": false
    }'
  ```

  ```javascript Node.js theme={null}
  const axios = require('axios');

  async function createWebhook() {
    try {
      const response = await axios.post(
        'https://api.insightssystem.com/api:qh9OQ3OW/webhook/dev/create',
        {
          webhooks: "https://your-domain.com/api/webhooks/whatsapp",
          status: true,
          incoming: true,
          outgoing: true,
          schedule_activity: false,
          waiting_duration: 0,
          active_signature: false
        },
        {
          headers: {
            'Content-Type': 'application/json',
            'Authorization': 'Bearer YOUR_TOKEN'
          }
        }
      );
      console.log(response.data);
      return response.data;
    } catch (error) {
      console.error('Error creating webhook:', error);
    }
  }

  createWebhook();
  ```

  ```python Python theme={null}
  import requests

  url = "https://api.insightssystem.com/api:qh9OQ3OW/webhook/dev/create"

  headers = {
      "Content-Type": "application/json",
      "Authorization": "Bearer YOUR_TOKEN"
  }

  data = {
      "webhooks": "https://your-domain.com/api/webhooks/whatsapp",
      "status": True,
      "incoming": True,
      "outgoing": True,
      "schedule_activity": False,
      "waiting_duration": 0,
      "active_signature": False
  }

  response = requests.post(url, headers=headers, json=data)
  print(response.json())
  ```
</CodeGroup>

#### Response

Returns a JSON object for the created webhook row.

<ResponseField name="id" type="number">
  Webhook ID.
</ResponseField>

<ResponseField name="status" type="boolean">
  Whether the webhook is enabled.
</ResponseField>

<ResponseField name="incoming" type="boolean">
  Incoming message trigger.
</ResponseField>

<ResponseField name="outgoing" type="boolean">
  Outgoing message trigger. When `true`, the endpoint receives messages your business sends, including WhatsApp Business app replies.
</ResponseField>

<ResponseField name="webhooks" type="string">
  Stored endpoint URL.
</ResponseField>

<ResponseField name="created_at" type="number">
  Unix timestamp in milliseconds.
</ResponseField>

<ResponseField name="waiting_duration" type="number">
  Schedule activity wait time in seconds.
</ResponseField>

<ResponseField name="schedule_activity" type="boolean">
  Schedule activity flag.
</ResponseField>

<ResponseField name="signature_secret" type="string | null">
  When `active_signature` was `true`: a **one-time** secret string — copy and store it immediately, it will not be retrievable again. When `active_signature` was `false`: `null`.
</ResponseField>

<CodeGroup>
  ```json With Signature (active_signature: true) theme={null}
  {
    "id": 1205,
    "status": true,
    "incoming": true,
    "outgoing": true,
    "webhooks": "https://your-domain.com/api/webhooks/whatsapp",
    "created_at": 1775471874139,
    "signature_secret": "<one-time secret — copy immediately>",
    "waiting_duration": 0,
    "schedule_activity": false
  }
  ```

  ```json Without Signature (active_signature: false) theme={null}
  {
    "id": 1205,
    "status": true,
    "incoming": true,
    "outgoing": true,
    "webhooks": "https://your-domain.com/api/webhooks/whatsapp",
    "created_at": 1775471874139,
    "signature_secret": null,
    "waiting_duration": 0,
    "schedule_activity": false
  }
  ```
</CodeGroup>

<Warning>
  When `active_signature` is `true`, the `signature_secret` is returned **only once** at creation time. Store it securely — it cannot be retrieved again. Use it to verify the authenticity of incoming webhook requests.
</Warning>

### Webhook Signature Verification

When a webhook is created with `active_signature: true`, every request our system sends to your endpoint will include an **`X-Webhook-Signature`** header. Use it to confirm the request genuinely came from us and was not tampered with.

| Header | Example value |
| - | - |
| `X-Webhook-Signature` | `RNEefV2V_tiDZeiOpeqMzWsR3X4zGOxIYARIF5-Ia2MXWIgT48jO-M4A1-bgr9bxdoHy5vb7azy_Vd-Gsp4qoAVhQCVyWZxhD1ZNJTQi9VNezJ6C7mnPy--osqcDSq1bfjjppAXBlyenWIa8_506ez5Z92p-eGucalu3-1g6wOk` |

The value is derived from the `signature_secret` returned at creation time. Compare it in your endpoint handler to validate each incoming request.

<Info>
  If `active_signature` was `false` when the webhook was created, this header will **not** be present in requests sent to your endpoint.
</Info>

<Warning>
  Never log or expose your `signature_secret` in client-side code or public repositories. If it is compromised, delete the webhook and create a new one with a fresh secret.
</Warning>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Webhook Not Receiving Events">
    * Verify your endpoint is publicly accessible
    * Check for HTTP 4xx or 5xx responses
    * Ensure proper SSL certificate configuration
    * Verify your webhook is enabled in the dashboard
    * Confirm **outgoing** is enabled if you expect events for messages you send (including the WhatsApp Business app)
  </Accordion>

  <Accordion title="No referral / Click-to-WhatsApp fields on the payload">
    * `referral` is usually only on the **first inbound message** after the ad click. Store `ctwa_clid` and `source_id` immediately.
    * Organic messages (not from an ad or post) have no `referral` object.
    * WhatsApp Status ad placements may omit `ctwa_clid` even when other referral fields are present.
    * Confirm you are looking at `referral` (Notifyer payload) or `messages[].referral` (Cloud API envelope), not a Facebook Lead Ad form submission — that is a different Meta product.
  </Accordion>

  <Accordion title="&#x22;Same webhook exist&#x22; error when creating a webhook">
    Each endpoint URL must be unique. If you submit a `webhooks` URL that is already registered, the API will return a **"Same webhook exist"** error.

    To resolve this:

    * Check your existing webhooks in the **Developer → Incoming Webhooks** tab of the dashboard to confirm whether the URL is already registered.
    * If you want to update settings on an existing webhook (e.g. toggle `incoming`, change `waiting_duration`), use the update/edit endpoint instead of re-creating it.
    * If you genuinely need a fresh webhook at the same URL, delete the existing one first, then create a new one.
  </Accordion>
</AccordionGroup>

## FAQs

<AccordionGroup>
  <Accordion title="Do webhooks include Click-to-WhatsApp ad details?">
    Yes. When the contact's message comes from a Click-to-WhatsApp ad, the payload includes a `referral` object (`source_id`, `source_url`, `source_type`, `headline`, `body`, `media_type`, creative URLs, and `ctwa_clid`). Use it to see which creative and platform produced the lead. Full reference: [Click-to-WhatsApp ads](#click-to-whatsapp-ads).
  </Accordion>

  <Accordion title="Do webhooks include messages typed in the WhatsApp Business app?">
    Yes. With [Meta WhatsApp Coexistence](/guides/notifyer-system/embedding-process#whatsapp-coexistence) you keep the WhatsApp Business app on your phone. Enable the **outgoing** trigger. Those messages arrive with `incoming_message: false`, `send_by: "WhatsApp App"`, and `was_message_by_human: true`. They are POSTed to your webhook — they are not limited to the Notifyer web UI.
  </Accordion>

  <Accordion title="How do I tell which teammate sent an outgoing message?">
    Read `send_by`. When the message was sent from the Notifyer chat inbox, `send_by` is that user's name (for example `"Axel Meta"`). When it was typed in the WhatsApp Business app, `send_by` is `"WhatsApp App"`. `was_message_by_human` is `true` in both human cases.
  </Accordion>

  <Accordion title="How do I handle different message types?">
    Check `message_type` (text, image, audio, video, document, location). For audio, the transcription appears in the text fields when available.
  </Accordion>

  <Accordion title="Do I need to respond to every webhook request?">
    Yes. Return a 2xx HTTP status code for every request so Notifyer does not retry unnecessarily.
  </Accordion>

  <Accordion title="How can I test webhook delivery?">
    Use the Test Webhook feature in the Developer section of your dashboard, or send a message from the WhatsApp Business app after enabling outgoing events.
  </Accordion>
</AccordionGroup>

<Card title="Need assistance?" icon="headset" href="mailto:support@whatsable.app">
  Our technical support team is available to assist with webhook configuration, payload handling, and integration questions.
</Card>


# Non-Template Message
Source: https://docs.whatsable.app/guides/notifyer-system/api/non-template-message

Send direct WhatsApp messages with text, media, and rich content without templates

<Tip>
  Send instant WhatsApp messages directly to your customers without requiring pre-approved templates. Perfect for quick responses, customer support, and media sharing during ongoing conversations.
</Tip>

The Send Non-Template Message API enables you to send immediate WhatsApp messages including text, images, videos, audio, and documents. This is ideal for customer support scenarios and ongoing conversations where template approval is not required.

## Overview

The Send Non-Template Message API enables you to:

* Send instant text messages with URL previews
* Share images, videos, and documents with captions
* Send audio files and voice messages
* Organize messages with custom labels for analytics
* Respond quickly in customer support scenarios
* Continue conversations without template restrictions

## Send Non-Template Message

Send various types of WhatsApp messages directly to a specific phone number without requiring pre-approved templates.

### Endpoint

```
POST https://api.insightssystem.com/api:U9ztporN/send/message
```

### Authentication

<Warning>
  All API requests require authentication using your API key. Never share your API keys in client-side code or public repositories.
</Warning>

Include your API key in all requests using Bearer authentication:

<CodeGroup>
  ```bash theme={null}
  Authorization: Bearer YOUR_API_KEY
  ```

  ```javascript theme={null}
  headers: {
    'Authorization': 'Bearer YOUR_API_KEY',
    'Content-Type': 'application/json'
  }
  ```
</CodeGroup>

### Request Body

<ParamField type="string">
  The recipient's phone number in international format with country code (e.g., "+15551234567").
</ParamField>

<ParamField type="string">
  The type of message to send. Must be one of: `text`, `image`, `video`, `audio`, `document`.
</ParamField>

<ParamField type="string">
  The type of recipient. Always use "individual" for single recipients.
</ParamField>

<ParamField type="string">
  The messaging platform. Always use "whatsapp".
</ParamField>

<ParamField type="array">
  Array of strings for message categorization and analytics (e.g., \["support", "urgent"]).
</ParamField>

### Message Type-Specific Parameters

<Tabs>
  <Tab title="Text Messages">
    <ParamField type="object">
      Text message configuration

      <Expandable title="Text Properties">
        <ParamField type="string">
          The text content of the message (max 4096 characters)
        </ParamField>

        <ParamField type="boolean">
          Whether to show URL previews for links in the message
        </ParamField>
      </Expandable>
    </ParamField>
  </Tab>

  <Tab title="Image Messages">
    <ParamField type="object">
      Image message configuration

      <Expandable title="Image Properties">
        <ParamField type="string">
          Public URL to the image file (JPG, JPEG, PNG)
        </ParamField>

        <ParamField type="string">
          Text caption for the image (max 1024 characters)
        </ParamField>
      </Expandable>
    </ParamField>
  </Tab>

  <Tab title="Video Messages">
    <ParamField type="object">
      Video message configuration

      <Expandable title="Video Properties">
        <ParamField type="string">
          Public URL to the video file (MP4, 3GPP)
        </ParamField>

        <ParamField type="string">
          Text caption for the video (max 1024 characters)
        </ParamField>
      </Expandable>
    </ParamField>
  </Tab>

  <Tab title="Audio Messages">
    <ParamField type="object">
      Audio message configuration

      <Expandable title="Audio Properties">
        <ParamField type="string">
          Public URL to the audio file (MP3, AAC, AMR, OGG)
        </ParamField>
      </Expandable>
    </ParamField>
  </Tab>

  <Tab title="Document Messages">
    <ParamField type="object">
      Document message configuration

      <Expandable title="Document Properties">
        <ParamField type="string">
          Public URL to the document file
        </ParamField>

        <ParamField type="string">
          Text caption for the document (max 1024 characters)
        </ParamField>

        <ParamField type="string">
          Custom filename for the document (with extension)
        </ParamField>
      </Expandable>
    </ParamField>
  </Tab>
</Tabs>

### Response

The API returns a detailed response indicating whether the message was accepted for delivery and provides WhatsApp message identifiers for tracking.

<ResponseField name="success" type="boolean">
  Indicates if the request was successfully processed
</ResponseField>

<ResponseField name="whatsapp_response_info" type="object">
  Details from the WhatsApp Business API about the message delivery

  <Expandable title="WhatsApp Response Fields">
    <ResponseField name="messaging_product" type="string">
      Always "whatsapp" for WhatsApp messages
    </ResponseField>

    <ResponseField name="contacts" type="array">
      Information about the message recipient

      <ResponseField name="input" type="string">
        The phone number that was provided in the request
      </ResponseField>

      <ResponseField name="wa_id" type="string">
        WhatsApp's unique identifier for the recipient
      </ResponseField>
    </ResponseField>

    <ResponseField name="messages" type="array">
      Details about the sent message

      <ResponseField name="id" type="string">
        Unique message identifier (wamid) for tracking status
      </ResponseField>

      <ResponseField name="message_status" type="string">
        Initial status of the message (typically "accepted")
      </ResponseField>
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="error" type="object">
  Present only when an error occurs

  <ResponseField name="code" type="string">
    Error code identifier
  </ResponseField>

  <ResponseField name="message" type="string">
    Human-readable error description
  </ResponseField>
</ResponseField>

### Example Requests

<Tabs>
  <Tab title="Text Message">
    <CodeGroup>
      ```bash cURL theme={null}
      curl -X POST \
        https://api.insightssystem.com/api:U9ztporN/send/message \
        -H 'Content-Type: application/json' \
        -H 'Authorization: Bearer YOUR_API_KEY' \
        -d '{
          "to": "+15551234567",
          "type": "text",
          "text": {
            "body": "Hello! Thank you for contacting our support team. How can we help you today?",
            "preview_url": true
          },
          "recipient_type": "individual",
          "messaging_product": "whatsapp",
          "labels": ["support", "greeting"]
        }'
      ```

      ```javascript Node.js theme={null}
      const apiKey = 'YOUR_API_KEY';

      async function sendTextMessage() {
        try {
          const response = await fetch('https://api.insightssystem.com/api:U9ztporN/send/message', {
            method: 'POST',
            headers: {
              'Content-Type': 'application/json',
              'Authorization': `Bearer ${apiKey}`
            },
            body: JSON.stringify({
              to: '+15551234567',
              type: 'text',
              text: {
                body: 'Hello! Thank you for contacting our support team. How can we help you today?',
                preview_url: true
              },
              recipient_type: 'individual',
              messaging_product: 'whatsapp',
              labels: ['support', 'greeting']
            })
          });
          
          const result = await response.json();
          console.log(result);
          return result;
        } catch (error) {
          console.error('Error sending message:', error);
        }
      }

      sendTextMessage();
      ```

      ```python Python theme={null}
      import requests

      url = "https://api.insightssystem.com/api:U9ztporN/send/message"
      api_key = "YOUR_API_KEY"

      payload = {
          "to": "+15551234567",
          "type": "text",
          "text": {
              "body": "Hello! Thank you for contacting our support team. How can we help you today?",
              "preview_url": True
          },
          "recipient_type": "individual",
          "messaging_product": "whatsapp",
          "labels": ["support", "greeting"]
      }

      headers = {
          "Content-Type": "application/json",
          "Authorization": f"Bearer {api_key}"
      }

      response = requests.post(url, json=payload, headers=headers)
      print(response.json())
      ```
    </CodeGroup>
  </Tab>

  <Tab title="Image Message">
    <CodeGroup>
      ```bash cURL theme={null}
      curl -X POST \
        https://api.insightssystem.com/api:U9ztporN/send/message \
        -H 'Content-Type: application/json' \
        -H 'Authorization: Bearer YOUR_API_KEY' \
        -d '{
          "to": "+15551234567",
          "type": "image",
          "image": {
            "link": "https://storage.googleapis.com/your-bucket/product-demo.jpg",
            "caption": "Here'\''s a visual guide to help you get started with our product!"
          },
          "recipient_type": "individual",
          "messaging_product": "whatsapp",
          "labels": ["support", "tutorial"]
        }'
      ```

      ```javascript Node.js theme={null}
      const apiKey = 'YOUR_API_KEY';

      async function sendImageMessage() {
        try {
          const response = await fetch('https://api.insightssystem.com/api:U9ztporN/send/message', {
            method: 'POST',
            headers: {
              'Content-Type': 'application/json',
              'Authorization': `Bearer ${apiKey}`
            },
            body: JSON.stringify({
              to: '+15551234567',
              type: 'image',
              image: {
                link: 'https://storage.googleapis.com/your-bucket/product-demo.jpg',
                caption: 'Here\'s a visual guide to help you get started with our product!'
              },
              recipient_type: 'individual',
              messaging_product: 'whatsapp',
              labels: ['support', 'tutorial']
            })
          });

          const result = await response.json();
          console.log(result);
          return result;
        } catch (error) {
          console.error('Error sending image:', error);
        }
      }

      sendImageMessage();
      ```
    </CodeGroup>
  </Tab>

  <Tab title="Video Message">
    <CodeGroup>
      ```bash cURL theme={null}
      curl -X POST \
        https://api.insightssystem.com/api:U9ztporN/send/message \
        -H 'Content-Type: application/json' \
        -H 'Authorization: Bearer YOUR_API_KEY' \
        -d '{
          "to": "+15551234567",
          "type": "video",
          "video": {
            "link": "https://storage.googleapis.com/your-bucket/tutorial-video.mp4",
            "caption": "Watch this step-by-step tutorial to get started quickly!"
          },
          "recipient_type": "individual",
          "messaging_product": "whatsapp",
          "labels": ["support", "tutorial"]
        }'
      ```

      ```javascript Node.js theme={null}
      const apiKey = 'YOUR_API_KEY';

      async function sendVideoMessage() {
        try {
          const response = await fetch('https://api.insightssystem.com/api:U9ztporN/send/message', {
            method: 'POST',
            headers: {
              'Content-Type': 'application/json',
              'Authorization': `Bearer ${apiKey}`
            },
            body: JSON.stringify({
              to: '+15551234567',
              type: 'video',
              video: {
                link: 'https://storage.googleapis.com/your-bucket/tutorial-video.mp4',
                caption: 'Watch this step-by-step tutorial to get started quickly!'
              },
              recipient_type: 'individual',
              messaging_product: 'whatsapp',
              labels: ['support', 'tutorial']
            })
          });

          const result = await response.json();
          console.log(result);
          return result;
        } catch (error) {
          console.error('Error sending video:', error);
        }
      }

      sendVideoMessage();
      ```

      ```python Python theme={null}
      import requests

      url = "https://api.insightssystem.com/api:U9ztporN/send/message"
      api_key = "YOUR_API_KEY"

      payload = {
          "to": "+15551234567",
          "type": "video",
          "video": {
              "link": "https://storage.googleapis.com/your-bucket/tutorial-video.mp4",
              "caption": "Watch this step-by-step tutorial to get started quickly!"
          },
          "recipient_type": "individual",
          "messaging_product": "whatsapp",
          "labels": ["support", "tutorial"]
      }

      headers = {
          "Content-Type": "application/json",
          "Authorization": f"Bearer {api_key}"
      }

      response = requests.post(url, json=payload, headers=headers)
      print(response.json())
      ```
    </CodeGroup>
  </Tab>

  <Tab title="Audio Message">
    <CodeGroup>
      ```bash cURL theme={null}
      curl -X POST \
        https://api.insightssystem.com/api:U9ztporN/send/message \
        -H 'Content-Type: application/json' \
        -H 'Authorization: Bearer YOUR_API_KEY' \
        -d '{
          "to": "+15551234567",
          "type": "audio",
          "audio": {
            "link": "https://storage.googleapis.com/your-bucket/voice-instructions.mp3"
          },
          "recipient_type": "individual",
          "messaging_product": "whatsapp",
          "labels": ["support", "voice-note"]
        }'
      ```

      ```javascript Node.js theme={null}
      const apiKey = 'YOUR_API_KEY';

      async function sendAudioMessage() {
        try {
          const response = await fetch('https://api.insightssystem.com/api:U9ztporN/send/message', {
            method: 'POST',
            headers: {
              'Content-Type': 'application/json',
              'Authorization': `Bearer ${apiKey}`
            },
            body: JSON.stringify({
              to: '+15551234567',
              type: 'audio',
              audio: {
                link: 'https://storage.googleapis.com/your-bucket/voice-instructions.mp3'
              },
              recipient_type: 'individual',
              messaging_product: 'whatsapp',
              labels: ['support', 'voice-note']
            })
          });
          
          const result = await response.json();
          console.log(result);
          return result;
        } catch (error) {
          console.error('Error sending audio:', error);
        }
      }

      sendAudioMessage();
      ```

      ```python Python theme={null}
      import requests

      url = "https://api.insightssystem.com/api:U9ztporN/send/message"
      api_key = "YOUR_API_KEY"

      payload = {
          "to": "+15551234567",
          "type": "audio",
          "audio": {
              "link": "https://storage.googleapis.com/your-bucket/voice-instructions.mp3"
          },
          "recipient_type": "individual",
          "messaging_product": "whatsapp",
          "labels": ["support", "voice-note"]
      }

      headers = {
          "Content-Type": "application/json",
          "Authorization": f"Bearer {api_key}"
      }

      response = requests.post(url, json=payload, headers=headers)
      print(response.json())
      ```
    </CodeGroup>
  </Tab>

  <Tab title="Document Message">
    <CodeGroup>
      ```bash cURL theme={null}
      curl -X POST \
        https://api.insightssystem.com/api:U9ztporN/send/message \
        -H 'Content-Type: application/json' \
        -H 'Authorization: Bearer YOUR_API_KEY' \
        -d '{
          "to": "+15551234567",
          "type": "document",
          "document": {
            "link": "https://storage.googleapis.com/your-bucket/user-manual.pdf",
            "caption": "Here is the complete user manual you requested.",
            "filename": "Product_User_Manual_v2.1.pdf"
          },
          "recipient_type": "individual",
          "messaging_product": "whatsapp",
          "labels": ["support", "documentation"]
        }'
      ```

      ```javascript Node.js theme={null}
      const apiKey = 'YOUR_API_KEY';

      async function sendDocumentMessage() {
        try {
          const response = await fetch('https://api.insightssystem.com/api:U9ztporN/send/message', {
            method: 'POST',
            headers: {
              'Content-Type': 'application/json',
              'Authorization': `Bearer ${apiKey}`
            },
            body: JSON.stringify({
              to: '+15551234567',
              type: 'document',
              document: {
                link: 'https://storage.googleapis.com/your-bucket/user-manual.pdf',
                caption: 'Here is the complete user manual you requested.',
                filename: 'Product_User_Manual_v2.1.pdf'
              },
              recipient_type: 'individual',
              messaging_product: 'whatsapp',
              labels: ['support', 'documentation']
            })
          });
          
          const result = await response.json();
          console.log(result);
          return result;
        } catch (error) {
          console.error('Error sending document:', error);
        }
      }

      sendDocumentMessage();
      ```

      ```python Python theme={null}
      import requests

      url = "https://api.insightssystem.com/api:U9ztporN/send/message"
      api_key = "YOUR_API_KEY"

      payload = {
          "to": "+15551234567",
          "type": "document",
          "document": {
              "link": "https://storage.googleapis.com/your-bucket/user-manual.pdf",
              "caption": "Here is the complete user manual you requested.",
              "filename": "Product_User_Manual_v2.1.pdf"
          },
          "recipient_type": "individual",
          "messaging_product": "whatsapp",
          "labels": ["support", "documentation"]
      }

      headers = {
          "Content-Type": "application/json",
          "Authorization": f"Bearer {api_key}"
      }

      response = requests.post(url, json=payload, headers=headers)
      print(response.json())
      ```
    </CodeGroup>
  </Tab>
</Tabs>

### Example Response

<CodeGroup>
  ```json Success Response theme={null}
  {
    "success": true,
    "whatsapp_response_info": {
      "messaging_product": "whatsapp",
      "contacts": [
        {
          "input": "+15551234567",
          "wa_id": "15551234567"
        }
      ],
      "messages": [
        {
          "id": "wamid.HBgLMTU1NTEyMzQ1NjcVAgAERgINQTlEOEJDNzM5QzQwAA==",
          "message_status": "accepted"
        }
      ]
    }
  }
  ```

  ```json Error Response theme={null}
  {
    "success": false,
    "error": {
      "code": "invalid_phone_number",
      "message": "The phone number format is invalid. Please use international format with country code."
    }
  }
  ```
</CodeGroup>

## Response Codes

<AccordionGroup>
  <Accordion title="200: Success">
    Your request was successful and the message has been accepted for delivery.
  </Accordion>

  <Accordion title="400: Bad Request">
    The request was invalid. Check the error message for details about missing or invalid parameters.

    ```json theme={null}
    {
      "success": false,
      "error": {
        "code": "missing_required_field",
        "message": "The 'to' field is required and must be a valid phone number"
      }
    }
    ```
  </Accordion>

  <Accordion title="401: Unauthorized">
    Authentication failed. Verify that you're using a valid API key in the Authorization header.

    ```json theme={null}
    {
      "success": false,
      "error": {
        "code": "unauthorized",
        "message": "Invalid API key provided"
      }
    }
    ```
  </Accordion>

  <Accordion title="403: Forbidden">
    Your account doesn't have permission to send messages or has reached its usage limit.
  </Accordion>

  <Accordion title="413: Payload Too Large">
    The media file or message content exceeds size limits.

    ```json theme={null}
    {
      "success": false,
      "error": {
        "code": "file_too_large",
        "message": "The media file exceeds the maximum allowed size"
      }
    }
    ```
  </Accordion>

  <Accordion title="422: Unprocessable Entity">
    The request contains invalid data or the media URL is not accessible.

    ```json theme={null}
    {
      "success": false,
      "error": {
        "code": "invalid_media_url",
        "message": "The provided media URL is not accessible"
      }
    }
    ```
  </Accordion>

  <Accordion title="429: Too Many Requests">
    You've exceeded the rate limit. Implement exponential backoff and retry logic.
  </Accordion>

  <Accordion title="500: Server Error">
    An internal server error occurred. Contact support if the issue persists.

    ```json theme={null}
    {
      "success": false,
      "error": {
        "code": "server_error",
        "message": "An internal server error occurred. Please try again later."
      }
    }
    ```
  </Accordion>
</AccordionGroup>

## Message Types Guide

Understanding the different message types and their optimal use cases will help you choose the right format for your communication needs.

### Text Messages

<CardGroup>
  <Card title="Best Practices" icon="shield-check">
    * Keep messages concise and actionable
    * Use URL previews for important links
    * Break long messages into multiple shorter ones
    * Include clear call-to-action when needed
  </Card>

  <Card title="Use Cases" icon="lightbulb">
    * Customer support responses
    * Order confirmations
    * Quick updates and notifications
    * FAQ responses
  </Card>
</CardGroup>

### Media Messages

<CardGroup>
  <Card title="Images" icon="image">
    * **Formats**: JPG, JPEG, PNG
    * **Max Size**: 5MB
    * **Optimal**: 1080x1080px or 16:9 ratio
    * **Use for**: Product photos, screenshots, infographics
  </Card>

  <Card title="Videos" icon="video">
    * **Formats**: MP4, 3GPP
    * **Max Size**: 16MB
    * **Max Duration**: 90 seconds
    * **Use for**: Tutorials, product demos, explanations
  </Card>

  <Card title="Audio" icon="volume-high">
    * **Formats**: MP3, AAC, AMR, OGG
    * **Max Size**: 16MB
    * **Max Duration**: 30 minutes
    * **Use for**: Voice messages, audio instructions
  </Card>

  <Card title="Documents" icon="file-text">
    * **Formats**: PDF, DOC, DOCX, PPT, PPTX, XLS, XLSX
    * **Max Size**: 100MB
    * **Use for**: Manuals, invoices, reports, contracts
  </Card>
</CardGroup>

## Media Requirements

<Warning>
  All media URLs must be publicly accessible via HTTPS without requiring authentication. For security-sensitive content, consider using signed URLs with expiration times.
</Warning>

### URL Requirements

<Steps>
  <Step title="Public Accessibility">
    Ensure your media URLs are publicly accessible without authentication headers or login requirements.
  </Step>

  <Step title="HTTPS Protocol">
    All media URLs must use HTTPS protocol. HTTP URLs will be rejected.
  </Step>

  <Step title="Direct File Access">
    URLs should point directly to the file, not to a page that contains the file or requires redirects.
  </Step>

  <Step title="Content-Type Headers">
    Your server should return appropriate Content-Type headers for media files to ensure proper handling.
  </Step>
</Steps>

### Supported Formats

| Media Type | Supported Formats | Max Size | Notes |
| - | - | - | - |
| Images | JPG, JPEG, PNG | 5MB | Animated GIFs not supported |
| Videos | MP4, 3GPP | 16MB | H.264 codec recommended |
| Audio | MP3, AAC, AMR, OGG | 16MB | Stereo or mono |
| Documents | PDF, DOC, DOCX, PPT, PPTX, XLS, XLSX | 100MB | Password-protected files not supported |

## Best Practices

<CardGroup>
  <Card title="Message Optimization" icon="rocket">
    Keep messages concise and actionable. Use rich media when it adds value. Always include clear next steps or calls-to-action when appropriate.
  </Card>

  <Card title="Error Handling" icon="octagon-check">
    Implement comprehensive error handling with retries. Store failed messages for later retry. Monitor success rates and investigate patterns in failures.
  </Card>

  <Card title="Media Management" icon="server">
    Use CDN for media hosting to ensure fast loading. Implement media validation before sending. Consider file size optimization for better delivery rates.
  </Card>

  <Card title="Analytics & Tracking" icon="chart-bar">
    Use labels consistently for message categorization. Track message IDs for delivery status monitoring. Implement webhook handling for real-time status updates.
  </Card>
</CardGroup>

## Security Considerations

<CardGroup>
  <Card title="API Key Security" icon="key">
    * Never expose API keys in client-side code
    * Use environment variables for key storage
    * Rotate keys regularly
    * Implement IP whitelisting when possible
  </Card>

  <Card title="Data Privacy" icon="shield-halved">
    * Avoid sending sensitive data in message content
    * Use secure, time-limited URLs for confidential documents
    * Implement proper access controls
    * Follow GDPR and other privacy regulations
  </Card>
</CardGroup>

## FAQs

<AccordionGroup>
  <Accordion title="Can I send messages to users who haven't messaged me first?">
    Non-template messages can only be sent to users who have initiated a conversation with your WhatsApp Business account within the last 24 hours. For proactive messaging, use the [Template Message API](/api-reference/notifier-system/templates/send-template-message).
  </Accordion>

  <Accordion title="Why are my media messages failing?">
    Common reasons include: media URL not publicly accessible, incorrect file format, file size exceeding limits, or missing Content-Type headers. Ensure your media URLs return proper HTTP responses and correct MIME types.
  </Accordion>

  <Accordion title="How do I track message delivery status?">
    Use the message ID returned in the response to track status via webhooks or the [Message Status API](/api-reference/notifier-system/message-status). The initial response only confirms WhatsApp accepted the message, not final delivery.
  </Accordion>

  <Accordion title="Can I schedule messages for later delivery?">
    This API sends messages immediately. For scheduled messaging, implement your own scheduling logic or use our [Scheduled Messages API](/api-reference/notifier-system/scheduled-messages).
  </Accordion>

  <Accordion title="What happens if the recipient doesn't have WhatsApp?">
    Messages will fail if sent to phone numbers without active WhatsApp accounts. The API will return an error indicating the recipient is not reachable on WhatsApp.
  </Accordion>

  <Accordion title="How do I handle different time zones for my recipients?">
    Consider implementing timezone-aware sending in your application logic. Send messages during business hours in the recipient's local timezone for better engagement rates.
  </Accordion>
</AccordionGroup>

<Card title="Need help?" icon="headset" href="mailto:team@whatsable.app">
  Our support team is available 24/7 to help with API integration, troubleshooting, or any questions about sending messages.
</Card>


# Phone replies in WhatsApp Business app still hit your webhook
Source: https://docs.whatsable.app/guides/notifyer-system/api/outbound-whatsapp-app

Keep answering on your phone in the WhatsApp Business app — your n8n, Make, or Zapier webhook still receives the message. Learn the three fields that identify it and how to filter for it.

<Tip>
  A reply typed by hand in the **WhatsApp Business app** is still POSTed to your webhook. Your n8n, Make, or Zapier automation still runs.
</Tip>

## The job

You (or a teammate) can keep answering customers directly from the phone, in the WhatsApp Business app — you don't need to delete it. [Meta WhatsApp Coexistence](/guides/notifyer-system/embedding-process#whatsapp-coexistence) keeps that number working in the app and in Notifyer System at once.

Those phone replies are **outgoing** messages, and Notifyer sends them to your webhook or automation trigger when outgoing events are enabled — even though no bot, template, or Notifyer chat inbox was involved. This page shows the exact fields that mark a reply as "typed in the app," and how to filter on them in n8n, Make, or Zapier.

## The three fields

A WhatsApp Business app reply carries this exact combination — `incoming_message: false` (outgoing), `send_by: "WhatsApp App"` (sent from the phone app, not a teammate or an automation), `was_message_by_human: true` (a person typed it, not a bot):

| Field | Value |
| - | - |
| `incoming_message` | `false` |
| `send_by` | `"WhatsApp App"` |
| `was_message_by_human` | `true` |

### Sample payload

Trimmed to the fields you need for filtering — same sanitized sample as the full payload reference:

```json theme={null}
{
  "last_messages": "[{\"type\":\"bot\",\"content\":\"Hello n8n\",\"timestamp\":\"2026-08-15T12:24:47.000Z\",\"content_type\":\"text\"},{\"type\":\"user\",\"content\":\"hi\",\"timestamp\":\"2026-08-12T12:27:42.746Z\",\"content_type\":\"text\"}]",
  "phone_number": 14155552671,
  "recipient_name": "Alex Martinez",
  "user_id": "158c59e1-ea85-4d0b-b70c-65328ba67a8e",
  "message_type": "text",
  "incoming_message": false,
  "send_by": "WhatsApp App",
  "was_message_by_human": true
}
```

<Note>
  The webhook sends more fields than shown here (`conversation_paragraph`, `last_message_of_user`, `note`, `labels`, and others) — see the [full payload reference](/guides/notifyer-system/api/incoming-message#payload-fields) for every field.
</Note>

## How to filter for it

### n8n

The Whatsable trigger is labeled **On new Incoming message event** — that's the node's name, not the direction of every event it fires. With outgoing enabled (credential **Notifyer System incoming and outgoing messages**), it also fires for phone-typed replies.

<Steps>
  <Step title="Add the trigger">
    Add the Whatsable node, pick **On new Incoming message event**, and connect the credential covering **Notifyer System incoming and outgoing messages** so outgoing events are included.
  </Step>

  <Step title="Add a Filter or IF node right after the trigger">
    Add a **Filter** (or **IF**) node immediately after the trigger.
  </Step>

  <Step title="Filter on the three fields">
    To match **only** phone-typed replies, add these conditions:

    ```text theme={null}
    {{ $json.incoming_message }}         is false
    {{ $json.send_by }}                  is equal to "WhatsApp App"
    ```

    To match **any** human-sent message (phone app or Notifyer chat inbox), use `{{ $json.was_message_by_human }}` is `true` instead, then branch on `{{ $json.send_by }}` to tell them apart.
  </Step>
</Steps>

Full walkthrough: [n8n overview](/guides/notifyer-system/n8n-overview).

### Make and Zapier

Same payload, same field names. Add a **Filter** (Zapier) or **Filter**/**Router** (Make) right after your trigger module, using the three fields above. See [Make overview](/guides/notifyer-system/make-overview) and [Zapier overview](/guides/notifyer-system/zapier-overview).

## Full payload reference

This page only covers filtering. For every field (`last_messages`, `conversation_paragraph`, `note`, `labels`, Click-to-WhatsApp `referral`, and more), see [Message webhooks](/guides/notifyer-system/api/incoming-message).

## Agent Skills

Automating webhook setup instead of using the dashboard? The `automate-notifyer` skill's `create-webhook.js` takes `--incoming` and `--outgoing` flags — enable both so your endpoint also receives WhatsApp Business app replies:

```bash theme={null}
node scripts/create-webhook.js --type dev \
  --url "https://your-endpoint.example.com/webhook" \
  --incoming --outgoing --signature
```

See [automate-notifyer](/guides/notifyer-system/agent-skills/automate-notifyer) for the full script reference.

## FAQs

<AccordionGroup>
  <Accordion title="Does &#x22;On new Incoming message event&#x22; mean the trigger only fires on inbound messages?">
    No — it's just the node's label. See [filtering in n8n](#n8n) above; check `incoming_message` for the actual direction, not the trigger name.
  </Accordion>

  <Accordion title="How do I tell a WhatsApp Business app reply apart from a Notifyer chat inbox reply?">
    Both are outgoing and human-sent — `send_by` is what separates them: `"WhatsApp App"` for the phone, or the teammate's name (for example `"Axel Meta"`) for the chat inbox.
  </Accordion>

  <Accordion title="Do I need to delete the WhatsApp Business app to use Notifyer System?">
    No. [Meta WhatsApp Coexistence](/guides/notifyer-system/embedding-process#whatsapp-coexistence) keeps the app and Notifyer System working on the same number at once.
  </Accordion>

  <Accordion title="My automation isn't firing for phone-typed replies. What should I check?">
    Confirm **outgoing** is enabled on the webhook or credential, then confirm your filter step isn't excluding `incoming_message: false` events by mistake. See [Message webhooks troubleshooting](/guides/notifyer-system/api/incoming-message#troubleshooting).
  </Accordion>
</AccordionGroup>

<Card title="Need assistance?" icon="headset" href="mailto:support@whatsable.app">
  Our technical support team is available to assist with webhook configuration, payload handling, and integration questions.
</Card>


# Template Message
Source: https://docs.whatsable.app/guides/notifyer-system/api/template-message

Send personalized WhatsApp messages using pre-approved templates

<Tip>
  Templates enable personalized communication while ensuring compliance with WhatsApp's business policies. This API lets you send template-based messages to your customers with dynamic content.
</Tip>

WhatsApp requires businesses to use pre-approved templates for initiating conversations. This API allows you to send template messages with personalized variables, media attachments, and interactive components to your customers.

## Overview

The Send Template Message API enables you to:

* Send WhatsApp messages using your pre-approved templates
* Dynamically replace variables with personalized content
* Attach media (images, videos, documents) when supported by the template
* Include interactive elements like buttons and quick replies
* Track delivery status through WhatsApp response information

<Card title="Try it in the API Reference" icon="arrow-right" href="https://docs.whatsable.app/api-reference/notifier-system/templates/send-template-message">
  Experiment with the Send Template Message API and view responses in real-time
</Card>

## Send Template Message

Send a personalized WhatsApp template message to a specific phone number.

### Endpoint

```
POST https://api.insightssystem.com/api:hFrjh8a1/send_template_message_by_api
```

### Authentication

<Warning>
  All API requests require authentication using your API key. Never share your API keys in client-side code.
</Warning>

Include your API key in all requests using Bearer authentication:

<CodeGroup>
  ```bash theme={null}
  Authorization: Bearer YOUR_API_KEY
  ```

  ```javascript theme={null}
  headers: {
    'Authorization': 'Bearer YOUR_API_KEY',
    'Content-Type': 'application/json'
  }
  ```
</CodeGroup>

### Request Body

<ParamField type="string">
  The unique identifier of the template to use. You can retrieve this from the [Get Templates API](/api-reference/notifier-system/templates/get-templates).
</ParamField>

<ParamField type="string">
  The recipient's phone number in international format with country code (e.g., "+123476529999").
</ParamField>

<ParamField type="object">
  Object containing key-value pairs for template variables. The keys must match the variable names defined in your template.

  <Expandable title="Variable Types">
    <ParamField type="string">
      Text variables that replace placeholders in the message body (e.g., body1, body2, etc.)
    </ParamField>

    <ParamField type="string">
      Text variables that replace placeholders in the message header
    </ParamField>

    <ParamField type="string">
      Public URL to media content (image, video, or document) for templates with media support
    </ParamField>

    <ParamField type="string">
      Set to "1" to enable dynamic button links in interactive templates
    </ParamField>
  </Expandable>
</ParamField>

### Response

The API returns a detailed response indicating whether the message was accepted for delivery and provides WhatsApp message identifiers for tracking.

<ResponseField name="success" type="boolean">
  Indicates if the request was successfully processed
</ResponseField>

<ResponseField name="whatsapp_response_info" type="object">
  Details from the WhatsApp Business API about the message delivery

  <Expandable title="WhatsApp Response Fields">
    <ResponseField name="messaging_product" type="string">
      Always "whatsapp" for WhatsApp messages
    </ResponseField>

    <ResponseField name="contacts" type="array">
      Information about the message recipient

      <ResponseField name="input" type="string">
        The phone number that was provided in the request
      </ResponseField>

      <ResponseField name="wa_id" type="string">
        WhatsApp's unique identifier for the recipient
      </ResponseField>
    </ResponseField>

    <ResponseField name="messages" type="array">
      Details about the sent message

      <ResponseField name="id" type="string">
        Unique message identifier (wamid) for tracking status
      </ResponseField>

      <ResponseField name="message_status" type="string">
        Initial status of the message (typically "accepted")
      </ResponseField>
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="error" type="object">
  Present only when an error occurs

  <ResponseField name="code" type="string">
    Error code identifier
  </ResponseField>

  <ResponseField name="message" type="string">
    Human-readable error description
  </ResponseField>
</ResponseField>

### Example Request

<CodeGroup>
  ```bash cURL theme={null}
  curl -X POST \
    'https://api.insightssystem.com/api:hFrjh8a1/send_template_message_by_api' \
    -H 'Content-Type: application/json' \
    -H 'Authorization: Bearer YOUR_API_KEY' \
    -d '{
      "template": "f10695a9-38d6-4f5f-8444-1f7bf52c6164",
      "phone_number": "+123476529999",
      "variables": {
        "body1": "Axel",
        "body2": "Shampoo",
        "body3": "$1",
        "media": "https://drive.google.com/file/d/1D35uTbceRPmCgwxVfBJZ2yxD2lQgs0bi/view?usp=sharing",
        "visit_website": "1"
      }
    }'
  ```

  ```javascript Node.js theme={null}
  const fetch = require("node-fetch");

  async function sendTemplateMessage() {
    try {
      const response = await fetch(
        'https://api.insightssystem.com/api:hFrjh8a1/send_template_message_by_api',
        {
          method: "POST",
          headers: {
            "Content-Type": "application/json",
            Authorization: "Bearer YOUR_API_KEY",
          },
          body: JSON.stringify({
            template: "f10695a9-38d6-4f5f-8444-1f7bf52c6164",
            phone_number: "+123476529999",
            variables: {
              body1: "Axel",
              body2: "Shampoo",
              body3: "$1",
              media: "https://drive.google.com/file/d/1D35uTbceRPmCgwxVfBJZ2yxD2lQgs0bi/view?usp=sharing",
              visit_website: "1"
            }
          }),
        }
      );
      const data = await response.json();
      console.log(data);
      return data;
    } catch (error) {
      console.error('Error sending template message:', error.response?.data || error.message);
    }
  }

  sendTemplateMessage();
  ```

  ```python Python theme={null}
  import requests

  url = "https://api.insightssystem.com/api:hFrjh8a1/send_template_message_by_api"

  payload = {
      "template": "f10695a9-38d6-4f5f-8444-1f7bf52c6164",
      "phone_number": "+123476529999",
      "variables": {
          "body1": "Axel",
          "body2": "Shampoo",
          "body3": "$1",
          "media": "https://drive.google.com/file/d/1D35uTbceRPmCgwxVfBJZ2yxD2lQgs0bi/view?usp=sharing",
          "visit_website": "1"
      }
  }

  headers = {
      "Content-Type": "application/json",
      "Authorization": "Bearer YOUR_API_KEY"
  }

  response = requests.post(url, json=payload, headers=headers)
  print(response.json())
  ```

  ```go Go theme={null}
  package main

  import (
  	"bytes"
  	"encoding/json"
  	"fmt"
  	"io/ioutil"
  	"net/http"
  )

  func main() {
  	url := "https://api.insightssystem.com/api:hFrjh8a1/send_template_message_by_api"
  	
  	// Create request payload
  	payload := map[string]interface{}{
  		"template": "f10695a9-38d6-4f5f-8444-1f7bf52c6164",
  		"phone_number": "+123476529999",
  		"variables": map[string]interface{}{
  			"body1":        "Axel",
  			"body2":        "Shampoo",
  			"body3":        "$1",
  			"media":        "https://drive.google.com/file/d/1D35uTbceRPmCgwxVfBJZ2yxD2lQgs0bi/view?usp=sharing",
  			"visit_website": "1",
  		},
  	}
  	
  	// Convert payload to JSON
  	jsonPayload, err := json.Marshal(payload)
  	if err != nil {
  		fmt.Println("Error creating JSON payload:", err)
  		return
  	}
  	
  	// Create request
  	req, err := http.NewRequest("POST", url, bytes.NewBuffer(jsonPayload))
  	if err != nil {
  		fmt.Println("Error creating request:", err)
  		return
  	}
  	
  	// Add headers
  	req.Header.Set("Content-Type", "application/json")
  	req.Header.Set("Authorization", "Bearer YOUR_API_KEY")
  	
  	// Send request
  	client := &http.Client{}
  	resp, err := client.Do(req)
  	if err != nil {
  		fmt.Println("Error sending request:", err)
  		return
  	}
  	defer resp.Body.Close()
  	
  	// Read response
  	body, err := ioutil.ReadAll(resp.Body)
  	if err != nil {
  		fmt.Println("Error reading response:", err)
  		return
  	}
  	
  	fmt.Println("Response:", string(body))
  }
  ```
</CodeGroup>

### Example Response

<CodeGroup>
  ```json Success Response theme={null}
  {
    "success": true,
    "whatsapp_response_info": {
      "messaging_product": "whatsapp",
      "contacts": [
        {
          "input": "+123476529999",
          "wa_id": "123476529999"
        }
      ],
      "messages": [
        {
          "id": "wamid.HBgLMTIzNDc2NTI5OTk5FQIAERgSNUU2RjM4NzM1M0Q5OEIwQTQwAA==",
          "message_status": "accepted"
        }
      ]
    }
  }
  ```

  ```json Error Response theme={null}
  {
    "success": false,
    "error": {
      "code": "invalid_template",
      "message": "The template ID provided does not exist or is not approved"
    }
  }
  ```
</CodeGroup>

## Response Codes

<AccordionGroup>
  <Accordion title="200: Success">
    Your request was successful and the message has been accepted for delivery.
  </Accordion>

  <Accordion title="400: Bad Request">
    The request was invalid. Check the error message for details.

    ```json theme={null}
    {
      "success": false,
      "error": {
        "code": "invalid_request",
        "message": "Missing required field: template"
      }
    }
    ```
  </Accordion>

  <Accordion title="401: Unauthorized">
    Authentication failed. Check that you're using a valid API key.

    ```json theme={null}
    {
      "success": false,
      "error": {
        "code": "unauthorized",
        "message": "Invalid API key provided"
      }
    }
    ```
  </Accordion>

  <Accordion title="403: Forbidden">
    Your account doesn't have permission to send messages.
  </Accordion>

  <Accordion title="404: Not Found">
    The template specified doesn't exist.

    ```json theme={null}
    {
      "success": false,
      "error": {
        "code": "template_not_found",
        "message": "Template with ID 'f10695a9-38d6-4f5f-8444-1f7bf52c6164' not found"
      }
    }
    ```
  </Accordion>

  <Accordion title="422: Unprocessable Entity">
    The request was well-formed but contains invalid parameters.

    ```json theme={null}
    {
      "success": false,
      "error": {
        "code": "invalid_phone_number",
        "message": "The phone number format is invalid"
      }
    }
    ```
  </Accordion>

  <Accordion title="429: Too Many Requests">
    You've exceeded the rate limit. Implement exponential backoff in your requests.
  </Accordion>

  <Accordion title="500: Server Error">
    Something went wrong on our end. Please contact support if the issue persists.

    ```json theme={null}
    {
      "success": false,
      "error": {
        "code": "server_error",
        "message": "An internal server error occurred"
      }
    }
    ```
  </Accordion>
</AccordionGroup>

## Working with Template Variables

Templates contain placeholders that are replaced with dynamic content when sending messages. Understanding how to map your data to these variables is essential.

### Variable Types

<CardGroup>
  <Card title="Text Variables" icon="text">
    Body and header variables replace text placeholders in your template. They are named `body1`, `body2`, etc., or `header1`, `header2`, etc.
  </Card>

  <Card title="Media Variables" icon="photo-film">
    Media variables allow you to attach images, videos, or documents to your template. Provide a public URL in the `media` property.
  </Card>

  <Card title="Button Variables" icon="hand-pointer">
    Used for dynamic buttons in interactive templates. Use `visit_website` set to "1" to enable dynamic button URLs.
  </Card>

  <Card title="Quick Reply Variables" icon="message-dots">
    For templates with quick reply buttons, provide the text to display on each button.
  </Card>
</CardGroup>

### Variable Mapping

<Steps>
  <Step title="Identify template variables">
    Examine your template structure to identify which variables are required. You can find this information using the [Get Templates API](/api-reference/notifier-system/templates/get-templates).
  </Step>

  <Step title="Prepare your data">
    Format your data to match the expected variable structure. Ensure values meet any length or format requirements.
  </Step>

  <Step title="Map data to variables">
    Create a `variables` object with keys matching your template's variable names and values from your data.
  </Step>

  <Step title="Handle media properly">
    For media templates, ensure your media URL is publicly accessible and in a WhatsApp-supported format.
  </Step>
</Steps>

## Media Guidelines

When including media in your templates, follow these guidelines for optimal delivery:

<CardGroup>
  <Card title="Images" icon="image">
    * Supported formats: JPG, JPEG, PNG
    * Max size: 5MB
    * Recommended aspect ratio: 1.91:1
  </Card>

  <Card title="Videos" icon="video">
    * Supported formats: MP4, 3GPP
    * Max size: 16MB
    * Max duration: 1 minute
  </Card>

  <Card title="Documents" icon="file">
    * Supported formats: PDF, DOC, DOCX, PPT, PPTX, XLS, XLSX
    * Max size: 100MB
  </Card>

  <Card title="URLs" icon="link">
    * Must be publicly accessible
    * Direct file links (no redirects)
    * HTTPS required
  </Card>
</CardGroup>

<Warning>
  Media URLs must be publicly accessible without requiring authentication. For security, we recommend using signed URLs with limited-time access.
</Warning>

## Best Practices

<CardGroup>
  <Card title="Error Handling" icon="shield-exclamation">
    Implement comprehensive error handling to manage API failures gracefully. Always check the `success` field in responses and handle various error scenarios.
  </Card>

  <Card title="Message Tracking" icon="chart-line">
    Store the returned `message_id` values to track delivery status using the [Message Status API](/api-reference/notifier-system/message-status).
  </Card>

  <Card title="Throttling" icon="gauge-high">
    Implement request throttling when sending to multiple recipients to avoid hitting rate limits and ensure reliable delivery.
  </Card>

  <Card title="Template Testing" icon="flask">
    Test your templates with various inputs to ensure variables are correctly replaced and messages appear as expected.
  </Card>
</CardGroup>

## FAQs

<AccordionGroup>
  <Accordion title="Why was my message not delivered?">
    Messages may fail to deliver for several reasons: invalid phone number, recipient has blocked your WhatsApp Business number, template issues, or WhatsApp temporary service interruptions. Check the error code returned for specific details.
  </Accordion>

  <Accordion title="Can I send to non-WhatsApp users?">
    No, recipients must have an active WhatsApp account associated with the phone number you're sending to.
  </Accordion>

  <Accordion title="How do I know if my message was delivered?">
    The initial response only confirms that WhatsApp accepted the message. For actual delivery status, implement webhook handling using our [Webhooks API](/api-reference/webhook) or query the [Message Status API](/api-reference/notifier-system/message-status).
  </Accordion>

  <Accordion title="Can I edit a message after sending?">
    No, WhatsApp messages cannot be edited once sent. You would need to send a new message with the corrected information.
  </Accordion>
</AccordionGroup>

<Card title="Need help?" icon="headset" href="mailto:team@whatsable.app">
  Our support team is available 24/7 to assist with template issues, API integration, or any other questions.
</Card>


# Attio
Source: https://docs.whatsable.app/guides/notifyer-system/attio-overview

Learn how to sync WhatsApp conversations with Attio CRM using the Notifyer System

# Notifyer System Integration with Attio

<Frame>
  <img alt="Attio Sync Settings screen in Notifyer showing CRM Record Matching with Person object and Phone numbers field" />
</Frame>

<Tip>
  This guide walks you through connecting Notifyer System with Attio so WhatsApp conversations show up inside your CRM — matched to the right contact, logged as a note, and kept up to date as messages are sent and received.
</Tip>

## Prerequisites

Before getting started, make sure you have:

<CardGroup>
  <Card title="Notifyer System Account" icon="user">
    Active Notifyer System account with a connected WhatsApp number and subscription plan (Pro or Agency)
  </Card>

  <Card title="Attio Workspace" icon="user">
    Access to an [Attio](https://attio.com/) workspace, with permission to install and authorize third-party apps
  </Card>
</CardGroup>

<Info>
  Your WhatsApp number must already be connected inside Notifyer before you start the Attio integration. If you haven't done that yet, complete the [embedding process](/guides/notifyer-system/embedding-process) first.
</Info>

<Tip>
  New to Notifyer System? [Sign up here](https://console.notifyer-systems.com/)
</Tip>

## What you get with this integration

<CardGroup>
  <Card title="Automatic contact matching" icon="magnifying-glass">
    Every WhatsApp message is matched to the right Attio record by phone number — no manual lookup needed
  </Card>

  <Card title="Auto-created contacts" icon="user-plus">
    New WhatsApp senders that don't exist in your CRM yet can be created automatically, with their name and phone number filled in
  </Card>

  <Card title="Conversations logged as notes" icon="note-sticky">
    Incoming and outgoing messages are written into an Attio Note on the matching record, so your team can read conversation history without leaving Attio
  </Card>

  <Card title="Live CRM fields" icon="arrows-rotate">
    Last message, timestamps, labels, country, and more update on the record — visible in your People list
  </Card>

  <Card title="One click to the full conversation" icon="up-right-from-square">
    A Live Chat Link field on every record opens the complete WhatsApp thread in Notifyer's live console, already matched to that contact
  </Card>

  <Card title="Full control over the mapping" icon="table-columns">
    You choose which Attio object and which attributes receive WhatsApp data — nothing is hard-coded to People only
  </Card>
</CardGroup>

<Frame>
  <img alt="Attio People list showing WhatsApp last message and timestamp columns kept up to date" />
</Frame>

## Setting up your Notifyer System account

<Steps>
  <Step title="Complete the embedding process">
    Before any WhatsApp message can sync anywhere, you must complete the platform [embedding process](/guides/notifyer-system/embedding-process), which connects your WhatsApp Business account to Notifyer System.

    <Info>
      The embedding process is required by Meta to ensure proper business verification and compliance with WhatsApp Business Platform policies.
    </Info>
  </Step>
</Steps>

<Note>
  Unlike the Pipedrive and Monday.com integrations, the Attio integration does not currently include an action to send WhatsApp template messages from inside Attio. Attio is a sync-in integration today: WhatsApp conversations flow into Attio automatically, but sending messages still happens from the Notifyer chat console, Zapier, Make, n8n, or the Whatsable API. You do not need to set up message templates specifically for Attio.
</Note>

## Connect Notifyer System to Attio

<Steps>
  <Step title="Open the Attio integration page">
    1. Log in to your **Notifyer Console**
    2. In the left sidebar, look for **Attio** in your list of connected tools (you'll see a **New** badge next to it)
    3. Click **Attio**, or open it directly at [notifyer.whatsable.app/attio](https://notifyer.whatsable.app/attio)

    <Info>
      If you're going through the onboarding checklist for the first time, you'll also find an **Attio** card under **Connect Tools** with the description "See your messages inside Attio Notes and schedule follow-ups."
    </Info>
  </Step>

  <Step title="Start the connection">
    On the Attio integration page, click **Connect Attio** (it may read **Authorize Attio** if your workspace was already installed but not yet authorized by you — both start the same OAuth flow).
  </Step>

  <Step title="Authorize Notifyer in Attio">
    You'll be redirected to Attio's authorization screen. Review the requested access and approve the connection so Notifyer can read and write records, attributes, and notes in your workspace.
  </Step>

  <Step title="Confirm the connection">
    After you approve, Attio redirects you back to the Notifyer Console. You'll land on a green **Attio workspace connected** card showing:

    * **Workspace** — your Attio workspace name, slug, and logo
    * **Authorized by** — the name and email of the teammate who connected the account
    * **Connected at** — the date and time the connection was made

    <Check>
      If you see this card, your Attio workspace is linked to Notifyer System. Continue below to configure how WhatsApp data flows into it.
    </Check>
  </Step>
</Steps>

<Warning>
  Until **Sync Settings** and **Attribute Mapping** are fully configured and saved, Notifyer will not sync WhatsApp messages into Attio. Required fields are marked with a red asterisk (**\***). If anything is missing, **Save settings** shows a validation error.
</Warning>

## Sync Settings reference

Once connected, scroll to **Sync Settings**. This is where you tell Notifyer which Attio object and fields should receive your WhatsApp data.

| Setting | Options | Description |
| - | - | - |
| **Object** (CRM Record Matching) | Person / Company / Deal / User / Workspace, or any custom object | The Attio object incoming WhatsApp numbers are matched against. This also drives auto-create |
| **Phone field** (CRM Record Matching) | Any phone-number attribute on the selected object | Field used to match a WhatsApp number to a record. Only phone-type attributes appear here |
| **Note Destination** | Any object in your workspace | Which Attio object receives the synced WhatsApp conversation note |
| **Note grouping** | Date-wise notes / Combined note | Whether messages are split into a new note per calendar day, or kept in one ongoing note |
| **Auto-create person** | On / Off | Whether Notifyer creates a new record when an incoming WhatsApp number has no match |
| **Timezone** | Any IANA timezone (e.g. `Asia/Dhaka`, `America/New_York`) | Used for message timestamps and for where one "day" starts and ends in date-wise mode |

### CRM Record Matching

<Steps>
  <Step title="Choose your Object">
    Open the **Object** dropdown and pick the Attio object you want WhatsApp contacts matched against. Every object in your workspace appears here — native ones like **Person**, **Company**, **Deal**, **User**, and **Workspace** are labeled **Native**, and anything you built yourself is labeled **Custom**.

    <Tip>
      Most teams should choose **Person**. It's Attio's default object for individual contacts, and it has the most built-in features (activity feed, emails, calls, tasks) compared to a custom object.
    </Tip>

    After you pick an object, Notifyer shows: *"This object drives later sync actions, including auto-create."* That means new contacts are created on this object, and later settings (like Auto-create) refer back to it.
  </Step>

  <Step title="Choose the Phone field">
    Open the **Phone field** dropdown. It only lists attributes on your chosen object whose type is **phone number**. Attio stores phone numbers in that dedicated field type (with a country code selector), so only those attributes can reliably match a WhatsApp number.

    If the object you picked has no phone-number field yet, the dropdown is empty (common on **Deal** or some custom objects). In Attio, add a phone-number attribute to that object — or use the built-in **Phone numbers** field on Person — then return to Notifyer and refresh.

    Once selected, Notifyer confirms: *"WhatsApp numbers will be matched using the \[field] field on \[object]."*
  </Step>
</Steps>

### Note Destination and Note grouping

<Steps>
  <Step title="Pick where notes should be written">
    In **Note Destination**, choose the object that should receive the WhatsApp conversation note. In most setups this is the same object you picked for CRM Record Matching (for example Person), but you can point it elsewhere when contacts are linked to another object and you want the conversation there.

    Notifyer explains the behavior: *"If a contact is linked to \[match object], notes go to \[note destination]. With no link, notes are saved on \[match object]."*
  </Step>

  <Step title="Choose how messages are grouped">
    Pick one of the two **Note grouping** options:

    * **Date-wise notes** — a new note is created for each calendar day, titled like "WhatsApp Conversation - Jul 30, 2026." Useful for busy conversations you want to scan by day.
    * **Combined note** — every message with that contact lives in one growing note, with each line timestamped (for example "at 9:10 pm: message"). Useful when you want the full history in one place.
  </Step>
</Steps>

### Auto-create person

<Frame>
  <img alt="Attio Person profile showing Whatsable automatically creating a Person and WhatsApp Conversation note" />
</Frame>

Turn this toggle **on** if you want Notifyer to create a new record on your matched object whenever a WhatsApp number that doesn't exist in Attio messages you for the first time. Notifyer fills in the recipient's name (or "Unnamed person" if WhatsApp doesn't provide one) and their phone number, then logs the first message as a note.

Leave it **off** if you only want to sync conversations for contacts already in Attio — messages from unknown numbers are skipped, with no error and no partial record created.

<Info>
  Despite the label **Auto-create person**, creation always uses the object you selected under **CRM Record Matching** — not only Attio's Person object.
</Info>

### Timezone Settings

Select your timezone from the dropdown (for example `(GMT+6) Asia/Dhaka`). This controls how message times appear in Attio notes and mapped timestamp fields, and — for date-wise notes — where the boundary between "today" and "tomorrow" falls.

When every Sync Settings field and Attribute Mapping field below is complete, click **Save settings**. You'll see a **Configuration Updated** confirmation when the save succeeds.

## Attribute Mapping reference

Scroll to **Attribute Mapping**. Instead of writing WhatsApp data into fixed columns, you choose which Attio attribute each Notifyer data point should update.

<Frame>
  <img alt="Attribute Mapping section showing Name, last messages, timestamps, Labels, Country, Note, Automation Note, and Live chat link" />
</Frame>

| WhatsApp / Notifyer data point | What gets written | Allowed attribute type |
| - | - | - |
| **Name column** | The contact's display name | `personal-name` (when the object is People/Person) or `text` (other objects) |
| **Last incoming message** | Most recent message text received from this contact | `text` |
| **Last outgoing message** | Most recent message text your team or AI sent | `text` |
| **Last incoming message time/date** | Timestamp of the last received message | `timestamp` |
| **Last outgoing message time/date** | Timestamp of the last sent message | `timestamp` |
| **Labels** | Labels assigned to the conversation in Notifyer | `text` |
| **Country** | Country detected from the contact's phone number | `text` |
| **Note** | The chat note from Notifyer for that contact (if any) | `text` |
| **Automation Note** | A note injected by an upstream automation rule, if one applies | `text` |
| **Live chat link** | Clickable link that opens this contact's full conversation in Notifyer's live console | `text` |

<Steps>
  <Step title="Select an attribute for each field">
    For every row, open the dropdown and choose an attribute on your matched object. If you need a purpose-built field (for example a custom "Last incoming message" text attribute), create it in Attio first, then refresh Notifyer.

    Each option shows a badge: **System** for Attio built-in attributes, **Custom** for attributes you or your team created.
  </Step>

  <Step title="Avoid duplicate mappings">
    Each Attio attribute can be used only once across the mapping. If it's already assigned elsewhere, it shows as **Already used** and can't be selected again.
  </Step>

  <Step title="Save your settings">
    When every required field in **Sync Settings** and **Attribute Mapping** is filled in, click **Save settings**. You'll see **Configuration Updated** / *Sync settings have been saved successfully.*

    <Check>
      Your Attio sync is configured. Send yourself a test WhatsApp message before rolling it out to your team.
    </Check>
  </Step>
</Steps>

<Info>
  If any required field is empty, Notifyer highlights incomplete fields with a red border and shows **"Please complete all required fields."**
</Info>

## How matching and auto-create work

<Steps>
  <Step title="A WhatsApp message arrives or is sent">
    Notifyer checks the phone number against the **Phone field** on your **Object** in CRM Record Matching.
  </Step>

  <Step title="Match found">
    The message is logged to that record's note (per Note Destination and Note grouping), and every mapped attribute is updated on the record.
  </Step>

  <Step title="No match found, Auto-create is on">
    A new record is created on your matched object with the sender's name and phone number. Future messages from that number sync to this record — Notifyer does not create a second record for the same number.
  </Step>

  <Step title="No match found, Auto-create is off">
    The message is skipped. No record is created and no error is raised. Sync for that number starts only after the contact exists in Attio.
  </Step>
</Steps>

## Message logging behavior

<Frame>
  <img alt="Attio Note titled WhatsApp Conversation showing a threaded chat between Lisa Kraus and Axel" />
</Frame>

Every incoming and outgoing WhatsApp message is written into an Attio Note on the matching record:

* **Sender is shown correctly.** Incoming messages show the contact's name (or phone number if no name is available). Outgoing messages show the teammate who sent it, or **AI Assistant** when your AI bot replied.
* **Timestamps use your configured timezone.** In date-wise mode, the date is in the note title, so lines inside the note show time only. In combined mode, lines include a fuller time stamp (for example "at 8:41 pm, Jul 29, 2026").
* **Media-only messages** (image, document, or voice note with no caption) show the media link instead of a blank line.
* **Date-wise mode** creates a fresh note per day, titled "WhatsApp Conversation - \[date]."
* **Combined mode** keeps one ongoing note per contact. New messages are appended; the newest line is shown in bold so recent activity is easy to spot.

<Frame>
  <img alt="Attio note modal showing WhatsApp Conversation for Jul 30, 2026 on Axel's Person record" />
</Frame>

## Field auto-update reference

Beyond the conversation note, these mapped fields update on the matched (or newly created) record when a message is sent or received:

<CardGroup>
  <Card title="Last incoming / outgoing message" icon="message-lines">
    Text of the most recent message in each direction
  </Card>

  <Card title="Last incoming / outgoing timestamp" icon="clock">
    Exact time of the most recent message in each direction, in your configured timezone
  </Card>

  <Card title="Labels" icon="tags">
    Labels Notifyer has assigned to the conversation
  </Card>

  <Card title="Country" icon="earth-americas">
    Country detected from the contact's phone number
  </Card>

  <Card title="Note" icon="note-sticky">
    Chat note from Notifyer for that contact, when one exists
  </Card>

  <Card title="Automation Note" icon="robot">
    Populated only when a Notifyer automation rule injects a note; otherwise blank
  </Card>

  <Card title="Live Chat Link" icon="up-right-from-square">
    Always-current link to the full conversation for that contact
  </Card>
</CardGroup>

## The Live Chat Link

<Frame>
  <img alt="Promotional overview of Live Chat Link opening Whatsable Live Chat from Attio" />
</Frame>

Every synced record can include a **Live chat link** attribute — a clickable link that opens that contact's full WhatsApp conversation in Notifyer's live chat console.

<Steps>
  <Step title="Open the link from Attio">
    Click the **Live chat link** value on the record. It opens Notifyer's live console (for example at `chat.notifyer-systems.com`).
  </Step>

  <Step title="You're matched automatically">
    The link includes a phone-number reference. Notifyer opens the correct conversation automatically — you don't need to search for the contact.
  </Step>

  <Step title="The link cleans itself up">
    After the conversation loads, the URL parameter is removed so the address bar shows a clean URL with nothing exposed.
  </Step>

  <Step title="Log in if prompted">
    If you're not signed in to Notifyer in that browser, you'll be asked to log in first. After you sign in, open the link again from Attio to land on the conversation.
  </Step>
</Steps>

<Frame>
  <img alt="Notifyer live chat console for Axel showing labels, Human Agent / AI Assistant handoff, and AI summary" />
</Frame>

<Note>
  This is one click into the full conversation, not an embedded chat window inside Attio. Attio does not support embedding external apps via iframe, so the conversation opens in Notifyer's console in a new tab. From there, your team can see AI activity, hand off to a human, assign the chat, and manage labels — in Notifyer, not inside Attio itself.
</Note>

## Automation and workflows

Unlike the Monday.com integration, Attio does not yet expose native Whatsable triggers or actions inside Attio's Workflow Builder.

<Warning>
  **Coming soon.** Attio's Workflows SDK does not currently pass authentication context (such as a user or account ID) to workflow-triggered actions — only an API key is available, with no way to tie the run back to a specific Notifyer account. Until that is supported, we cannot ship the equivalent of Monday's "when a new WhatsApp message arrives → do something in Attio" workflow triggers and actions.
</Warning>

Today, build automation around Attio + WhatsApp through:

<CardGroup>
  <Card title="Zapier, Make, or n8n" icon="diagram-project">
    Connect Attio and Notifyer System through your automation platform — see the [Zapier](/guides/notifyer-system/zapier-overview), [Make](/guides/notifyer-system/make-overview), and [n8n](/guides/notifyer-system/n8n-overview) guides
  </Card>

  <Card title="The Whatsable API" icon="code">
    Call the [Notifyer System API](/guides/notifyer-system/api/template-message) from your backend or from an Attio automation that can reach external webhooks
  </Card>
</CardGroup>

## Known limitations

<AccordionGroup>
  <Accordion title="No native Attio Workflow triggers or actions yet" icon="diagram-project">
    Whatsable triggers and actions inside Attio Workflows are not available yet because Attio's workflow runtime does not provide the user/account authentication context Notifyer needs. Use Zapier, Make, n8n, or the Whatsable API for automation today.
  </Accordion>

  <Accordion title="No embedded chat panel inside Attio" icon="window-restore">
    Attio does not support iframe embeds, so Notifyer cannot render a live chat window inside Attio. Use the **Live chat link** attribute to open the full conversation in Notifyer's console instead.
  </Accordion>

  <Accordion title="Attio Notes cannot be patched in place" icon="note-sticky">
    Attio's note API does not support editing an existing note. Notifyer works around this by finding the note by title, reading its content, and rewriting it with the new message appended. Day to day this is invisible, but it can cause small formatting differences between older and newer lines. If someone deletes a WhatsApp conversation note in Attio, Notifyer creates a new one on the next message.
  </Accordion>

  <Accordion title="No send-template or schedule action from Attio" icon="paper-plane">
    You cannot send WhatsApp templates or schedule messages from inside Attio yet. Reply, schedule, and broadcast from the Notifyer chat console (or Zapier / Make / n8n / API).
  </Accordion>
</AccordionGroup>

## Disconnecting

To remove the connection, open **Attio** in your Notifyer Console and click **Disconnect Attio** on the connected workspace card.

<Warning>
  Disconnecting stops the sync immediately — no further WhatsApp messages are written to Attio until you reconnect.
</Warning>

To reconnect, repeat the [connection steps](#connect-notifyer-system-to-attio). After authorizing again, open **Sync Settings** and **Attribute Mapping**, confirm every required field, and click **Save settings** before relying on sync again.

## Best practices

<AccordionGroup>
  <Accordion title="Prefer the Person object for most teams" icon="user">
    Person is Attio's native contact object and usually already has a system **Phone numbers** field. Custom objects work too, but they need a phone-number attribute before matching can work.
  </Accordion>

  <Accordion title="Keep phone numbers in Attio's phone field type" icon="phone">
    Matching only uses Attio phone-number attributes (with country code). Don't store WhatsApp numbers in a plain text field if you need reliable matching.
  </Accordion>

  <Accordion title="Create clear custom attributes before mapping" icon="table-columns">
    Create purpose-built text and timestamp attributes in Attio (for example "Last incoming message", "Live chat link") before you map them in Notifyer. That keeps your People list easy to scan.
  </Accordion>

  <Accordion title="Test with one number before going live" icon="vial">
    After saving settings, send a test message from a known phone number and confirm the Attio record, note, and mapped fields update as expected.
  </Accordion>
</AccordionGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Connection succeeds, but no messages are syncing" icon="circle-exclamation">
    <Steps>
      <Step title="Check Object and Phone field">
        Open **Sync Settings** and confirm **Object** and **Phone field** under **CRM Record Matching** are set, and that the phone field holds the number you're testing with.
      </Step>

      <Step title="Confirm everything was saved">
        Every required Sync Settings and Attribute Mapping field must be filled. Click **Save settings** and wait for **Configuration Updated** before testing again.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Duplicate records are appearing for the same contact" icon="clone">
    <Steps>
      <Step title="Check phone formatting across records">
        Notifyer matches by phone number and should not create duplicates for the same number. If you see duplicates, check whether the same contact exists twice in Attio with different phone formats (with and without country code, for example).
      </Step>

      <Step title="Contact support">
        If duplicates persist, contact Whatsable support with both record IDs so we can investigate.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Timestamps look wrong" icon="clock-rotate-left">
    <Steps>
      <Step title="Check Timezone Settings">
        Open **Sync Settings** and confirm **Timezone** matches the timezone your team expects when reading messages.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Note formatting looks inconsistent" icon="note-sticky">
    <Steps>
      <Step title="This comes from an Attio API limitation">
        Attio does not support patching an existing note. Notifyer finds the note by title and rewrites it with new content appended. Small bold/spacing differences between older and newer lines can appear because of that workaround.
      </Step>

      <Step title="If a note was deleted">
        If someone deletes a WhatsApp conversation note in Attio, Notifyer creates a new one on the next message for that contact.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Phone field dropdown is empty" icon="phone-slash">
    <Steps>
      <Step title="Add a phone-number attribute in Attio">
        The **Phone field** dropdown only lists phone-number attributes on the selected object. If none exist (common on custom objects or Deal), add a phone-number attribute in Attio, then refresh the Notifyer settings page.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Live Chat Link opens a login screen" icon="lock">
    <Steps>
      <Step title="Sign in to Notifyer first">
        The Live Chat Link opens Notifyer's live console and requires a signed-in Notifyer session in that browser. Log in once, then open the link again from the Attio record.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="An attribute I want isn't showing in the mapping dropdown" icon="filter">
    <Steps>
      <Step title="Check the attribute type">
        Each mapping field only lists compatible types (for example `timestamp` for time/date fields, `text` for message fields, `personal-name` for Name on Person). Create an attribute of the correct type in Attio if needed.
      </Step>

      <Step title="Check it isn't already mapped">
        Attributes already used elsewhere show as **Already used**. Clear the other mapping first if you want to reuse that attribute.
      </Step>
    </Steps>
  </Accordion>
</AccordionGroup>

## Need help?

Our support team is ready to assist you:

<CardGroup>
  <Card title="Email support" icon="envelope" href="mailto:team@whatsable.app">
    Contact [team@whatsable.app](mailto:team@whatsable.app)
  </Card>

  <Card title="Schedule a demo" icon="calendar" href="https://tidycal.com/axelmeta/notifyer-systems-demo">
    Book a personalized walkthrough
  </Card>

  <Card title="Live chat" icon="message-dots" href="">
    Click the green chat button in the bottom right corner of the Notifyer System dashboard
  </Card>
</CardGroup>

<Info>
  For additional automation platform integrations (Make, Zapier, n8n, Pipedrive, Monday.com), please contact our support team or check our integration documentation.
</Info>


# Can I send WhatsApp template broadcasts with Whatsable?
Source: https://docs.whatsable.app/guides/notifyer-system/broadcasts

Send WhatsApp template broadcasts with Whatsable: CSV bulk recipients, delivery modes, scheduled send, basic stats, and Meta cold-outreach fences.

Yes. Whatsable sends **Meta-approved WhatsApp template broadcasts** to a CSV (or audience) list from your connected WhatsApp Business number. Broadcasting is the main job of the **Bulk Message** plan and is also on **Pro** and **Agency**. Use this page when you need the operator path: prepare the CSV, test, choose a delivery mode, launch or schedule, and read basic delivery stats.

Broadcasting is **not** the same as creating templates, and it is **not** a native multi-day drip builder. Templates are a separate topic; day-0 / day-3 / day-6 sequences run only through **Make, Zapier, or n8n**.

## Prerequisites

* **Whatsable account** on **Bulk Message**, **Pro**, or **Agency** — sign in at [dashboard.whatsable.app/signin](https://dashboard.whatsable.app/signin).
* **WhatsApp Business number connected** through Whatsable (Embedded Signup / Coexistence supported — keep the WhatsApp Business app; do not uninstall it after connect).
* **At least one Meta-approved message template** for that number. Only **super-admins** create templates; Meta must approve before the template appears in send flows. Editing an existing template is not supported — recreate and resubmit if you need changes.
* **Meta payment method** on the WhatsApp / Business Manager side. Template sends fail when Meta has no billing method for the number.
* **Active plan** (or trial) with enough **unique-contact** headroom for the recipient list. Whatsable bills unique contacts per month; Meta bills delivery fees separately at Meta rates (Whatsable **0% markup**).
* **CSV ready** (or list you will export): phone numbers with country code. Exact column rules are below.

<Info>
  How-to video (EN): [How to broadcast](https://youtu.be/_upLw2kKxLo). Broadcasting and templates are different topics — do not swap the videos.
</Info>

***

## Operator path — send a template broadcast

Open **Broadcasts** in the Whatsable console and follow the steps below. Menu labels can vary by workspace; use the Broadcasts area you see in the console.

### 1. Open Broadcasts and pick an approved template

In the Whatsable console, open **Broadcasts**. Start a new broadcast and select a **Meta-approved** template only. Pending templates will not send reliably; Graph “unsupported post request” on test send is often an unapproved template, not a disconnected number.

If the template uses body variables (`{{1}}`, `{{2}}`, …), you will map them from CSV columns in the next step.

### 2. Prepare the recipient CSV

Whatsable expects a CSV whose **phone column is named exactly `phone_number`**. Include the country code. Support troubleshooting locks this name; if the broadcast fails after upload, check formatting first.

**Required**

| Column | Rule |
| - | - |
| `phone_number` | Exact header. Digits with country code. In the upload path used by console/API tooling, omit the `+` prefix (example: `14155550101`, not `+14155550101`). |

**Optional (when the template needs them)**

| Column | Maps to |
| - | - |
| `body1`, `body2`, `body3`, … | Template body variables `{{1}}`, `{{2}}`, `{{3}}`, … per recipient |
| `media` | Public URL for per-recipient media when the template has a media header |
| `button_dynamic_url_value` | Per-recipient URL suffix for dynamic CTA buttons |

Example:

```csv theme={null}
phone_number,body1,body2
14155550101,John,12345
14155550102,Jane,67890
```

After you select a template in the console, download the **template CSV** from the broadcast UI when available — that file matches the variables Meta approved for that template.

**Upload behavior:**

* Duplicate phone numbers in the same CSV are **deduplicated** (kept once).
* Re-uploading recipients for the same broadcast **replaces** the previous list.
* The system returns **unique recipient count** and an estimated **cost of broadcast** (Meta-side country pricing) before you finalize.

Use the `phone_number` header above — do not substitute alternate names such as camelCase `phoneNumber`.

### 3. Send a test message

Before the full list, send a **test** to a number you control. Confirm the template renders (variables, media, buttons). Fix CSV or template issues here — not after a 10k launch.

### 4. Upload recipients and review counts

Upload the CSV. Confirm:

* Unique numbers match expectations (duplicates dropped).
* Estimated cost looks sane for the countries on the list.
* Unique count fits your Whatsable **unique-contact** tier (or accept overage — see plans page).

Some console flows let you scope recipients with labels when that control is present. Use the labels UI in your console when available.

### 5. Choose delivery mode

Whatsable paces outbound template traffic with three delivery modes (API/console values):

| Mode | Behavior | When to use |
| - | - | - |
| **smart** | Sends in batches; paces toward a target **read rate** before advancing | Default for larger lists — safer warm-up |
| **regular** | Fixed batch size at a steady pace (batch size is an integer; the console may expose a per-minute range — use the bounds shown in your console) | Predictable pace without read-rate feedback |
| **risk** | No batching — sends the list as a blast (confirm when prompted) | Tiny urgent lists only — large blasts can trigger Meta spam detection and temporarily disable the number |

Do **not** invent a Whatsable numeric RPM or “messages per second” product limit on this page. Meta messaging tier caps (business-initiated conversations per 24 hours) still apply — see rate-limits docs when published and Meta’s own tier rules.

### 6. Launch now or schedule

* **Send / launch** is available on **Bulk Message**, **Pro**, and **Agency**.
* **Scheduled broadcasts** (future send time) are available on **Bulk Message**, **Pro**, and **Agency**. Scheduling is **not** the same as a native drip delay chain.

Schedule strings on the finalize path use `DD/MM/YYYY HH:mm`. Timezone resolution can follow the caller’s environment — **always verify the resulting time in the console** after you save.

### 7. Monitor basic delivery stats

After launch, Whatsable shows **basic delivery analytics**: **sent / delivered / read** (Bulk Message and up). **Block rate** is **not** a Whatsable dashboard metric — check **Meta Business Manager**. Advanced analytics are a **Pro / Agency** surface, not Bulk Message.

Pause, resume, and cancel for an **ongoing** broadcast are **not** available in the current console path. Track basic **sent / delivered / read** stats and download results when your role allows. Upcoming scheduled sends can be removed on the API path when that endpoint is in use.

***

## Plan gates (broadcast-related)

| Capability | Bulk Message | Pro | Agency |
| - | - | - | - |
| Broadcast / CSV bulk with approved templates | Yes | Yes | Yes |
| Basic sent / delivered / read | Yes | Yes | Yes |
| Scheduled broadcast (future send) | Yes | Yes | Yes |
| Shared 2-way inbox / seats / AI / integrations | No | Yes | Yes |

Canonical money and full unique-contact tiers: [whatsable.app/pricing](https://whatsable.app/pricing). Plan matrix docs: [plans Bulk Message / Pro / Agency](/guides/notifyer-system/plans-bulk-message-pro-agency).

***

## Cold outreach and deliverability (Meta)

For **cold** lists (contacts who have never messaged the business), **especially US numbers**, Meta may choose **not** to deliver if the recipient has not engaged before. Ideally the contact has messaged first. European numbers often fare somewhat better than US for cold reach, but **any** fully cold list still risks poor deliverability or flags.

**Warm gradually:** for cold or new-number campaigns, prefer **smart** (or modest **regular**) pacing over **risk** blasts. Gradual send helps warm the number and reduces throttling / block risk. This is Meta deliverability behavior — not a Whatsable “US block” product toggle.

***

## Limits and what broadcasts are NOT

<Warning>
  **Scheduled broadcast ≠ drip.** Future send time is available on broadcast plans; multi-day drip delays are **not** “schedule” — see below.
</Warning>

* **No native drip builder.** Day-0 / day-3 / day-6 (or similar) sequences are built in **Make, Zapier, or n8n**; Whatsable sends each template when the automation fires. Do not describe an in-product drip / delay campaign builder.
* **No typing-indicator dots** claim for broadcast (or product-wide as a Whatsable surface).
* **Do not invent Whatsable RPM** numbers here.
* **Do not invent UI chrome** (library redesign tabs, Craft wizard labels, Upcoming wrap, Switch, Numbers Meta reports) that is not present in your console.
* **Broadcast ≠ templates.** Creating / approving templates is a separate operator page. Only approved templates send.
* **Bulk Message** has no team inbox, AI, or integrations — replies to broadcast recipients are not a Bulk Message inbox workflow.
* **Group Messaging** is unavailable / waitlist only — not a live broadcast substitute.
* **Competitor comparisons** and Meta per-country cent tables are out of scope; Meta fees pass through at **0%** markup.

***

## Related

<CardGroup>
  <Card title="Plans: Bulk Message, Pro, Agency" href="/guides/notifyer-system/plans-bulk-message-pro-agency">
    Who gets broadcast, schedule, inbox, AI, and unique-contact billing.
  </Card>

  <Card title="Pricing (canonical money)" href="https://whatsable.app/pricing">
    Live prices, contact tiers, overage, and annual toggle.
  </Card>

  <Card title="Message templates" href="/guides/notifyer-system/message-templates">
    Create and approve WhatsApp templates (separate from broadcasting).
  </Card>

  <Card title="API: send template message" href="/guides/notifyer-system/api/template-message">
    Programmatic single-recipient template send (not the CSV broadcast wizard).
  </Card>

  <Card title="Make overview" href="/guides/notifyer-system/make-overview">
    External sequences / drips — Pro and Agency.
  </Card>

  <Card title="Zapier overview" href="/guides/notifyer-system/zapier-overview">
    External sequences / drips — Pro and Agency.
  </Card>

  <Card title="Connect WhatsApp (Coexistence)" href="/guides/whatsable/connect-whatsapp-coexistence">
    Keep the Business app while using the API.
  </Card>

  <Card title="Team inbox" href="/guides/notifyer-system/team-inbox">
    Shared 2-way inbox on Pro and Agency (not Bulk Message).
  </Card>
</CardGroup>

***

## FAQ

### Which plans can send CSV / template broadcasts?

**Bulk Message**, **Pro**, and **Agency**. Broadcasting is the main Bulk Message use case. **Scheduled** future sends are included on those plans.

### What CSV columns does Whatsable require?

The phone column must be named exactly **`phone_number`** (country code; omit `+` on the upload path). Add **`body1`**, **`body2`**, … for template variables, plus **`media`** or **`button_dynamic_url_value`** when the template needs them. Prefer the downloadable template CSV from the broadcast UI after you pick a template.

### Why did my broadcast fail after I uploaded a CSV?

Almost always **CSV formatting**: wrong header (not `phone_number`), missing country code, or variable columns not named `body1`, `body2`, …. Also confirm the template is **approved** and Meta has a **payment method**.

### Can I build a day-0 / day-3 / day-6 drip inside Whatsable?

**No native drip builder.** Build the delays in **Make, Zapier, or n8n**; Whatsable sends each message. Scheduled broadcast is a **single** future send time, not a drip chain.

### Will Meta deliver cold US campaigns?

Meta **may not deliver** cold outreach to US numbers when recipients have never engaged. Warm gradually (prefer **smart** / modest **regular** over **risk** blasts). Ideally contacts message you first.

### Where do I see block rate?

In **Meta Business Manager**, not as a Whatsable analytics metric. Whatsable basic stats = **sent / delivered / read**.

### Is broadcasting the same as the template API?

No. The console **CSV broadcast** flow uploads a list and paces delivery. The [template message API](/guides/notifyer-system/api/template-message) sends to one recipient per request. Agent-skills / automation scripts can orchestrate the same three backend steps the console uses; that is advanced automation, not a substitute for reading this operator page.


# Can I assign WhatsApp chats to teammates in Whatsable?
Source: https://docs.whatsable.app/guides/notifyer-system/chat-assignment

Assign WhatsApp chats to teammates in Whatsable via Zapier, Make, API, keywords, or AI content. Pro/Agency seats, assigned-only push, and limits.

Yes. On **Pro** and **Agency**, Whatsable lets you **assign a WhatsApp conversation to a teammate** so the right person owns the thread. Assignment is available through **Zapier**, **Make**, the **API**, **keyword rules** on labels, and **AI** that routes by conversation content. Use this page when you need the inventory of those assign paths — not a rewrite of the shared inbox UI.

**Bulk Message** has **no** shared 2-way inbox and **no** team seats, so chat assignment does not apply there. Extra inbox seats (when you need more people than the plan includes) are **\$12 per seat per month** on Pro and Agency and include native Android/iOS apps plus **mobile push only for chats assigned to that person**.

For how the shared inbox looks day to day (who sees what, labels vs notes, AI ↔ human handoff), see [Team inbox](/guides/notifyer-system/team-inbox).

## Prerequisites

* **Whatsable plan:** **Pro** or **Agency** (shared inbox, seats, AI, and integrations). **Bulk Message** = broadcast-only — no inbox / seats / assign.
* **Connected WhatsApp Business number** through Whatsable (Embedded Signup / Coexistence supported — keep the WhatsApp Business app; do not uninstall it after connect).
* **Teammates on the account** (or extra seats added when you need more people in the inbox). Plan price covers the included team; buy seats when you need more.
* **For automation assign:** a **Zapier**, **Make**, **n8n**, or **API** connection authenticated with your Whatsable API key — integrations are Pro/Agency only.
* **For keyword / AI assign:** labels (and AI chatbot / handoff settings) configured in the console so routing rules and the bot have something to act on.

<Info>
  Canonical seat money: **\$12 / seat / mo** on Pro and Agency. Do not confuse seats with unique-contact overage or Group Messaging (**\$16 / group**, unavailable / waitlist). Live pricing: [whatsable.app/pricing](https://whatsable.app/pricing).
</Info>

***

## Assign paths — full inventory

Whatsable does **not** document a separate named “Assign to” control on every surface the same way. You **can** assign a chat to a teammate via the paths below, and you can **add or remove labels** from the same automation partners. Inbox operators often route work with **labels** (for example a teammate name label or a routing label your automations watch). Treat labels and teammate assignment as related ownership tools.

### 1. Zapier — Update a Contact

From a Zap, use Whatsable **Update a Contact**. The Zapier action description states you can **assign the conversation to someone on your team**, add notes, and **add/remove labels**.

**Documented fields on this page’s field dictionary:** Phone Number, Display Name, Add a Note, Add Label Names or IDs, Remove Label Names or IDs.

Update a Contact can assign the conversation to a teammate — confirm any assignee control in your live Zap editor.

Typical pattern: a form, CRM stage change, or Lead Ad trigger decides the owner in Zapier, then Update a Contact assigns (and optionally labels) the WhatsApp chat in Whatsable.

### 2. Make — Update a Contact

Make’s Update a Contact description also covers **assign to a teammate**, notes, and **add/remove labels**.

**Documented module fields today:** Phone Number, Display Name, Note, Add Labels, Remove Labels.

Confirm any assignee control in your live Make module.

### 3. API and Agent Skills

Assignment via **API** works alongside Zapier and Make. Operator scripts under **chat-notifyer** Agent Skills update conversation **labels** on the recipient (`assign-label.js` / `remove-label.js`) and can drive handoff by applying the bot’s **handoff label**. Labels on the Whatsable chat are string names on the recipient record.

Use Agent Skills when you are building or operating from code / an IDE agent — not as a substitute customer mobile app. Point developers to [chat-notifyer](/guides/notifyer-system/agent-skills/chat-notifyer) for script-level label and handoff operations.

### 4. n8n (partner flow)

From an n8n workflow you can **add/remove labels** and **assign the chat to a teammate** the same way as Zapier and Make. Confirm any assignee control in your live n8n node.

### 5. Keywords in chat

**Assignment by keywords in chat** rides on **label keyword rules**: when you create a label with keyword rules, Whatsable can automatically apply that label when an incoming message matches. Teams use keyword labels (and teammate / routing labels) so the right people see and own the thread — including label-scoped Team Member visibility in the inbox.

Manual label assign from automations or Agent Skills can override auto-applied labels; keyword auto-labelling continues on later messages.

### 6. AI by conversation content

**AI can assign by conversation content.** The AI chatbot (and ProactiveBot on Pro/Agency) can **create, edit, and remove conversation labels** from what the customer says — for example applying a routing or handoff label when the conversation matches your plain-language instructions (“if they mention a fleet of 10+ vehicles, hand to a human”).

Distinguish carefully:

| Concept | What it means |
| - | - |
| **Teammate / chat assignment** | Which person on your team owns the WhatsApp thread (this page). |
| **Bot Assign** | Which AI bot is attached to a conversation in the contact panel — required for the bot to reply on pre-existing chats. See [AI chatbot configuration](/guides/notifyer-system/ai-chatbot/configuration). |
| **Chat Handoff / Let the agent reply** | Whether the AI or a human is actively answering that chat. Covered on [Team inbox](/guides/notifyer-system/team-inbox) and AI docs — not rewritten here. |

### 7. Partner-flow owner routing (examples only)

You can **build** owner routing in Zapier, Make, or n8n — for example **round-robin across sales**, or map a **Facebook Lead Ad / form / ad source** to the right teammate — then **assign and label** the WhatsApp chat in Whatsable.

Whatsable does **not** ship a native “round-robin engine” or built-in Lead-Ad→teammate UI — build that routing in the partner tool, then assign in Whatsable.

### 8. Inbox + mobile (how assignment shows up)

* **Shared team inbox** (Pro/Agency): teammates collaborate in the Whatsable inbox. Labels organize and scope visibility; see [Team inbox](/guides/notifyer-system/team-inbox) for access layers (number · Admin vs chat-only · label scope).
* **Native Android / iOS apps** (with extra seats): **push notifications only for chats assigned to that person**. Push-only does **not** mean the app hides other chats.

***

## Limits and what assignment is NOT

<Warning>
  **Bulk Message = no seats / no shared inbox.** Chat assignment, team seats, and assigned-only push start at **Pro** and **Agency**.
</Warning>

* **No CRM ↔ Whatsable bidirectional label / tag mirror** product. Labels live on the Whatsable chat; Monday, Pipedrive, Zapier, Make, n8n, Agent Skills, and the AI can read or write Whatsable labels so inbox + mobile + automations stay aligned — that is **not** a two-way sync of CRM tags as one store.
* On Agency, up to 100 WhatsApp numbers sit on one subscription, and each additional number added to that same subscription is \$5. The inbox can show all numbers or one number, and you can limit each teammate to specific numbers.
* **Push-only ≠ app hides other chats.** Assigned-only push notifies for owned work; it does not claim a visibility lockdown that removes unassigned chats from the app.
* **No WhatsApp typing-indicator dots** claim. Response Delay 5–60s is a separate AI setting — not assignment.
* A full roles / permissions matrix beyond the locked facts on this page (super-admin creates templates; Admin vs chat-only / label scope on team-inbox) is not documented here.
* **Bot Assign ≠ teammate assign.** Do not conflate AI bot attachment with human ownership.
* **Native round-robin / Lead-Ad router** requires naming Zapier, Make, or n8n — Whatsable does not ship that router UI.
* **Group Messaging \$16** is unavailable — not a team-assign substitute.

***

## Related

<CardGroup>
  <Card title="Team inbox" icon="inbox" href="/guides/notifyer-system/team-inbox">
    Shared 2-way inbox on Pro and Agency — who sees what, labels, AI ↔ human handoff.
  </Card>

  <Card title="Zapier overview" icon="bolt" href="/guides/notifyer-system/zapier-overview">
    Update a Contact — labels, notes, assign capability.
  </Card>

  <Card title="Make overview" icon="diagram-project" href="/guides/notifyer-system/make-overview">
    Update a Contact — labels, notes, assign capability.
  </Card>

  <Card title="Zapier fields" icon="table" href="/guides/notifyer-system/zapier-fields">
    Field dictionary — assign capability.
  </Card>

  <Card title="Make fields" icon="table" href="/guides/notifyer-system/make-fields">
    Field dictionary — assign capability.
  </Card>

  <Card title="AI chatbot configuration" icon="robot" href="/guides/notifyer-system/ai-chatbot/configuration">
    Bot Assign, knowledge, handoff — distinct from teammate chat assignment.
  </Card>

  <Card title="Plans: Bulk Message, Pro, Agency" icon="credit-card" href="/guides/notifyer-system/plans-bulk-message-pro-agency">
    Plan gates for inbox, seats, AI, and integrations.
  </Card>

  <Card title="chat-notifyer Agent Skills" icon="terminal" href="/guides/notifyer-system/agent-skills/chat-notifyer">
    Script-level labels, handoff, and conversation ops.
  </Card>
</CardGroup>

Also: [Pricing](https://whatsable.app/pricing) · [n8n overview](/guides/notifyer-system/n8n-overview) · [Message webhooks](/guides/notifyer-system/api/incoming-message).

***

## FAQ

### Can I assign WhatsApp chats to teammates in Whatsable?

**Yes — on Pro and Agency.** Assign via **Zapier**, **Make**, the **API**, **keyword** label rules, or **AI** by conversation content. Bulk Message has no shared inbox or seats.

### Does Bulk Message include chat assignment or seats?

**No.** Bulk Message is one-way broadcast / CSV. Shared inbox, seats, assign, AI, and integrations start at **Pro** (and Agency).

### Is there a named “Assign to” field in Zapier or Make?

**Yes, as a capability.** Update a Contact’s product description includes assigning a teammate. Documented dictionary fields today are phone, display name, note, and add/remove labels. Confirm any assignee control in your live editor.

### Do mobile push notifications fire for every chat?

**No.** Extra seats include push **only for chats assigned to that person**. That does **not** mean the mobile app hides other chats.

### Is teammate assignment the same as Bot Assign?

**No.** **Bot Assign** picks which AI bot is attached to a conversation. **Teammate assignment** decides which human owns the thread. Both can matter on the same chat.

### Can Whatsable round-robin chats natively?

**Not as a built-in Whatsable router UI.** Build round-robin (or Lead Ad → owner) in **Zapier, Make, or n8n**, then assign and label the chat in Whatsable.

### Do CRM tags stay in two-way sync with Whatsable labels?

**No bidirectional CRM↔Whatsable label mirror product.** Labels live on the Whatsable conversation; partners and the AI can read/write those Whatsable labels so inbox, mobile, and automations stay aligned.

### How much is an extra inbox seat?

**\$12 per seat per month** on Pro and Agency (native Android/iOS + assigned-only push + assign paths above). Confirm on [pricing](https://whatsable.app/pricing).


# Embedding Process
Source: https://docs.whatsable.app/guides/notifyer-system/embedding-process

Connect your WhatsApp Business Account to Notifyer System. Meta WhatsApp Coexistence is supported — you do not need to delete the WhatsApp Business app on your phone.

# WhatsApp Business Account Integration

<Frame>
  <iframe title="WhatsApp Business Integration" />
</Frame>

## Overview

Notifyer System enables businesses to send automated WhatsApp messages to customers through a direct integration with the WhatsApp Business Platform. This guide walks you through the embedding process to connect your WhatsApp Business Account with Notifyer System.

<Note>
  This process uses Meta's Embedded Signup flow, which allows you to create or connect your WhatsApp Business Account directly within Notifyer System.
</Note>

## Prerequisites

<Check>
  A Notifyer System account. No active subscription required. You can add a plan or pay-as-you-go credit later.
</Check>

<Check>
  Meta Business Portfolio (or willingness to create one during the process)
</Check>

<Check>
  A business phone number you control. If that number already uses the **WhatsApp Business app**, keep the app — Notifyer supports Meta WhatsApp Coexistence
</Check>

## WhatsApp Coexistence

<Info>
  **Meta WhatsApp Coexistence is supported on Notifyer System.** You do **not** need to delete the WhatsApp Business app or stop using the number on your phone. After Embedded Signup, the same number works in the WhatsApp Business app, the Notifyer chat inbox, and automations (Make, Zapier, n8n, API, and webhooks) at the same time.
</Info>

You can connect a number that is **already active** in the WhatsApp Business app. After Embedded Signup:

* Keep chatting with customers from the WhatsApp Business app on your phone
* Use the Notifyer chat inbox and team inboxes in the browser
* Send and receive through Make, Zapier, n8n, the API, and [webhooks](/guides/notifyer-system/api/incoming-message)

Messages typed by hand in the WhatsApp Business app are delivered to your webhook. See `incoming_message`, `send_by`, and `was_message_by_human` in the [message webhook payload](/guides/notifyer-system/api/incoming-message).

<Note>
  Coexistence is a **Notifyer System** capability (your own WhatsApp Business number on the Cloud API). It is available on Notifyer System plans that complete Embedded Signup — not limited to a specific integration. Whatsable's own support number also runs on coexistence.
</Note>

<Warning>
  Coexistence applies to the **WhatsApp Business app** (the business client). If the number is registered on the consumer WhatsApp app instead, migrate it to WhatsApp Business or use a different number. You still do **not** delete the WhatsApp Business app to work with Notifyer.
</Warning>

## Integration Process

<Steps>
  <Step title="Access the Connection Flow">
    <Accordion title="Navigating to the Connection Page">
      1. Log in to your Notifyer System dashboard
      2. Navigate to **Your Templates** section
      3. Make sure you're on the **Connect to WhatsApp** tab
      4. Click the **Connect your WhatsApp Number** button in the center of the page

      <Frame>
        <img />
      </Frame>
    </Accordion>

    <Tip>
      You can track your progress through the onboarding process using the steps indicator in the bottom-left corner of the screen.
    </Tip>
  </Step>

  <Step title="Connect with Facebook">
    1. Log in with your Facebook account when prompted
    2. If already logged in, click **Continue as \[your Facebook username]**
    3. Review the permissions Notifyer System is requesting
    4. Click **Get Started** to begin the configuration process

    <Frame>
      <img alt="Connecting with Facebook" />
    </Frame>
  </Step>

  <Step title="Complete the 6-Step Configuration">
    <Accordion title="Step 1: Business Information" icon="building">
      <ResponseField name="Business Portfolio" type="dropdown">
        Select an existing business portfolio or create a new one
      </ResponseField>

      <Accordion title="Create a business portfolio" icon="circle-check">
        If you choose to create a new business portfolio, fill out the required fields:

        <ResponseField name="Business Name" type="string">
          Your official business name (must be unique among your portfolios)
        </ResponseField>

        <ResponseField name="Business Email Address" type="string">
          A valid email that can receive verification messages
        </ResponseField>

        <ResponseField name="Business Website or Profile" type="string">
          Your business website URL or social media profile
        </ResponseField>

        <ResponseField name="Country" type="string">
          Country where your business is located
        </ResponseField>

        <Frame>
          <img alt="Entering required information in Business Information section" />
        </Frame>
      </Accordion>

      <Accordion title="Existing Portfolios" icon="circle-check">
        Choose a business portfolio you've already configured in Meta Business Suite

        <Info>
          See how to [create a business portfolio in Meta Business Suite and Business Manager.](https://www.facebook.com/business/help/1710077379203657)

          If you select an existing portfolio, your business name, website, and country will be automatically populated from your Meta Business configuration.
        </Info>
      </Accordion>
    </Accordion>

    <Accordion title="Step 2: Select WhatsApp Business Account" icon="message">
      <ResponseField name="WhatsApp Business Account" type="radio">
        Select whether to create a new account or use an existing one
      </ResponseField>

      <Expandable title="Account Options">
        <ResponseField name="Create new account" type="option">
          **Recommended** for first-time users (default option)
        </ResponseField>

        <ResponseField name="Select existing account" type="option">
          Only available if you have existing WhatsApp Business accounts
        </ResponseField>
      </Expandable>

      <ResponseField name="WhatsApp Business Profile" type="radio">
        Select whether to create a new profile or use an existing one
      </ResponseField>

      <Expandable title="Profile Options">
        <ResponseField name="Create new profile" type="option">
          **Recommended** for first-time users (default option)
        </ResponseField>

        <ResponseField name="Select existing profile" type="option">
          Only available if you connect an existing WhatsApp Business profile
        </ResponseField>
      </Expandable>

      <br />

      <Frame>
        <img alt="Selecting options for WhatsApp Business Account and Profile" />
      </Frame>
    </Accordion>

    <Accordion title="Step 3: Business Profile Setup" icon="id-card">
      <ResponseField name="WhatsApp Business Account Name" type="string">
        The internal name of your account (used for management purposes)
      </ResponseField>

      <ResponseField name="WhatsApp Business Display Name" type="string">
        The name your customers will see when receiving messages from your business

        <Warning>
          This is the name your customers will see when receiving messages from your business. Choose carefully as it impacts brand recognition.
        </Warning>
      </ResponseField>

      <ResponseField name="Category" type="dropdown">
        Business category that best represents your industry (will be displayed on your profile)
      </ResponseField>

      <Frame>
        <img alt="Entering required information in Create a WhatsApp business profile section" />
      </Frame>
    </Accordion>

    <Accordion title="Step 4: Phone Number Configuration" icon="phone">
      <ResponseField name="Phone Number Method" type="radio">
        Choose how to add your phone number
      </ResponseField>

      <Expandable title="Phone Number Options">
        <ResponseField name="Add a new number (Recommended)" type="option">
          Use your own business phone number
        </ResponseField>

        <ResponseField name="Free WhatsApp number (Not Recommended)" type="option">
          WhatsApp will generate a +1 555 number (limited functionality)
        </ResponseField>
      </Expandable>

      <ResponseField name="Verification Method" type="radio">
        Choose how to receive your verification code
      </ResponseField>

      <Expandable title="Verification Options">
        <ResponseField name="Text message" type="option">
          Receive verification code via SMS
        </ResponseField>

        <ResponseField name="Phone call" type="option">
          Receive verification code via automated call
        </ResponseField>
      </Expandable>

      <br />

      <Frame>
        <img alt="Entering required informstion in Create a WhatsApp business profile section" />
      </Frame>
    </Accordion>

    <Accordion title="Step 5: Number Verification" icon="shield-check">
      Enter the verification code received via your selected method

      <Frame>
        <img alt="Entering required informstion in Create a WhatsApp business profile section" />
      </Frame>
    </Accordion>

    <Accordion title="Step 6: Payment Method Setup" icon="credit-card">
      1. After verification, you'll see a "You're now ready to chat with people on WhatsApp" screen
      2. Click the **Add Payment Method** button
      3. You'll be redirected to the Facebook Business "Billing & Payments" page
      4. Select "Payment Methods" from the left menu
      5. Ensure you're on the "WhatsApp Business accounts" tab
      6. Select your WhatsApp account from the dropdown (verify WhatsApp account ID)
      7. Click "Add Payment Method" and provide the required information
      8. Set your payment method as the default option
    </Accordion>
  </Step>

  <Step title="Complete Business Verification">
    <Warning>
      This step is critical for ensuring you can send messages without restrictions. Unverified businesses may experience limited functionality.
    </Warning>

    1. Navigate to Settings in your Facebook Business Manager
    2. Select "WhatsApp accounts" under the "Accounts" section
    3. Scroll down to the "Business verification" section
    4. Click "Start verification" to access the Security Center
    5. Complete the business verification process by providing the requested business information and documentation
  </Step>
</Steps>

## Account Dashboard Overview

Once your WhatsApp Business Account is connected, you'll have access to the following tabs in the "Your Templates" section:

<CardGroup>
  <Card title="Sign Up" icon="user-plus">
    Connect your WhatsApp Business Account using the "Sign up with Facebook" option
  </Card>

  <Card title="Create Template" icon="pen-to-square">
    Design message templates and submit them to Meta for approval
  </Card>

  <Card title="Templates" icon="clipboard-list">
    View, manage, and monitor the approval status of your message templates
  </Card>
</CardGroup>

## Integration Options

After successfully embedding your WhatsApp Business Account, you can integrate Notifyer System with your preferred automation platform:

<AccordionGroup>
  <Accordion title="Make Integration" icon="lines-leaning">
    Connect Notifyer System with Make to create powerful automation workflows.

    [View Make Documentation →](https://docs.whatsable.app/guides/notifyer-system/make-overview)
  </Accordion>

  <Accordion title="Zapier Integration" icon="bolt">
    Integrate with Zapier to connect WhatsApp messaging with thousands of applications.

    [View Zapier Documentation →](https://docs.whatsable.app/guides/notifyer-system/zapier-overview)
  </Accordion>

  <Accordion title="n8n Integration" icon="diagram-project">
    Use n8n for advanced workflow automation with WhatsApp messaging.

    [View n8n Documentation →](https://docs.whatsable.app/guides/notifyer-system/n8n-overview)
  </Accordion>

  <Accordion title="Direct API Integration" icon="code">
    Implement custom integrations using our comprehensive API.

    [Try API Reference →](https://docs.whatsable.app/api-reference/introduction)
  </Accordion>
</AccordionGroup>

## API Reference

<CardGroup>
  <Card title="Get Templates" icon="list" href="https://docs.whatsable.app/guides/notifyer-system/api/get-templates">
    Retrieve all your approved message templates
  </Card>

  <Card title="Send Template Message" icon="paper-plane" href="https://docs.whatsable.app/guides/notifyer-system/api/template-message">
    Send messages using your approved templates
  </Card>

  <Card title="Message webhooks" icon="inbox" href="/guides/notifyer-system/api/incoming-message">
    Incoming and outgoing messages, including replies typed in the WhatsApp Business app
  </Card>
</CardGroup>

<Card title="Try it in the API Reference" icon="arrow-right" href="https://docs.whatsable.app/api-reference/">
  Experiment with the Get Templates API and view responses in real-time
</Card>

## Alternative Option: Notifier

<Info>
  If the embedding process is too complex for your needs, you can use Notifier by Whatsable instead, which allows you to send automated messages through our WhatsApp bot without going through the full embedding process.
</Info>

<Card title="Learn More About Notifier" icon="lightbulb" href="https://docs.whatsable.app/guides/notifier/zapier">
  Discover a simpler way to send automated WhatsApp messages using Notifier by Whatsable
</Card>

## Troubleshooting

<Accordion title="Verification Failed" icon="triangle-exclamation">
  If your phone number verification fails:

  1. You do **not** need to delete the WhatsApp Business app. Coexistence is supported — keep using that app on your phone
  2. If the number is on the **consumer** WhatsApp app (not WhatsApp Business), switch it to WhatsApp Business or use a different number
  3. Wait 24 hours before trying again with the same number
  4. Try a different verification method (SMS vs. call)
  5. Contact support if issues persist
</Accordion>

<Accordion title="Business Verification Issues" icon="building-shield">
  If you encounter problems with business verification:

  1. Ensure all business information is accurate and matches official documents
  2. Provide clear, high-quality images of requested documentation
  3. Allow 1-2 business days for verification review
  4. Submit an appeal if verification is rejected
</Accordion>

## Resources

<CardGroup>
  <Card title="Meta Business Suite" icon="facebook" href="https://business.facebook.com">
    Manage your Meta business profiles and portfolios
  </Card>

  <Card title="WhatsApp Business Platform" icon="whatsapp" href="https://business.whatsapp.com/products/business-platform">
    Learn more about the WhatsApp Business Platform
  </Card>

  <Card title="Embedded Signup Guide" icon="link" href="https://developers.facebook.com/docs/whatsapp/embedded-signup">
    Meta's official documentation on embedded signup
  </Card>
</CardGroup>

## Need help?

Our support team is ready to assist you:

<CardGroup>
  <Card title="Email support" icon="envelope" href="mailto:team@whatsable.app">
    Contact [team@whatsable.app](mailto:team@whatsable.app)
  </Card>

  <Card title="Schedule a demo" icon="calendar" href="https://tidycal.com/axelmeta/whatsapp-notifications-by-whatsable">
    Book a personalized walkthrough
  </Card>

  <Card title="Live chat" icon="message-dots" href="https://console.notifyer-systems.com/">
    Click the chat button in the bottom right corner of the Notifyer System dashboard
  </Card>
</CardGroup>


# Enterprise Customization
Source: https://docs.whatsable.app/guides/notifyer-system/enterprise/customization

Learn how to customize Notifyer System for your enterprise needs

# Enterprise Customization

Notifyer System provides extensive customization options for enterprise-level WhatsApp messaging.

## Customization Features

### Branding

* Custom templates
* Brand colors
* Logo integration
* Custom fonts
* Brand voice
* Message styling
* Media assets

### Workflow

* Custom workflows
* Business rules
* Automation rules
* Integration points
* Custom scripts
* Event handlers
* Process automation

### Integration

* Custom APIs
* Webhook endpoints
* SDK customization
* Plugin system
* Custom connectors
* Data mapping
* Format conversion

## Customization Implementation

### Custom Template

```javascript theme={null}
// Example: Creating a custom template
const createCustomTemplate = async (template) => {
  try {
    const response = await axios.post(
      'https://api.notifiersystem.com/v1/templates',
      {
        name: template.name,
        language: template.language,
        category: template.category,
        components: [
          {
            type: 'HEADER',
            format: 'IMAGE',
            example: {
              header_url: [template.headerImage]
            }
          },
          {
            type: 'BODY',
            text: template.body,
            variables: template.variables
          },
          {
            type: 'BUTTON',
            sub_type: 'URL',
            index: '0',
            parameters: template.buttonParameters
          }
        ],
        customizations: {
          branding: template.branding,
          styling: template.styling,
          metadata: template.metadata
        }
      },
      {
        headers: {
          'Authorization': `Bearer ${process.env.NOTIFIER_SYSTEM_API_KEY}`,
          'Content-Type': 'application/json',
          'X-Tenant-ID': process.env.TENANT_ID
        }
      }
    );
    return response.data;
  } catch (error) {
    console.error('Error creating template:', error);
    throw error;
  }
};
```

### Custom Workflow

```javascript theme={null}
// Example: Implementing a custom workflow
const processCustomWorkflow = async (message) => {
  try {
    // Apply business rules
    const rules = await getBusinessRules(message.tenant_id);
    const processedMessage = applyBusinessRules(message, rules);

    // Apply custom transformations
    const transformedMessage = await applyCustomTransformations(processedMessage);

    // Apply automation rules
    const automationRules = await getAutomationRules(message.tenant_id);
    const automatedMessage = applyAutomationRules(transformedMessage, automationRules);

    // Send the message
    return await sendMessage(automatedMessage);
  } catch (error) {
    console.error('Error processing workflow:', error);
    throw error;
  }
};
```

## Best Practices

### Branding

* Maintain consistency
* Follow guidelines
* Test templates
* Monitor performance
* Update regularly
* Document changes
* Version control

### Workflow

* Keep it simple
* Document processes
* Test thoroughly
* Monitor performance
* Handle errors
* Regular review
* Continuous improvement

### Integration

* Use standards
* Document APIs
* Version control
* Test integration
* Monitor performance
* Handle errors
* Regular updates

## Monitoring

### Customization Monitoring

* Template performance
* Workflow efficiency
* Integration status
* Error rates
* Response times
* User feedback
* ROI metrics

### Business Impact

* Message effectiveness
* User engagement
* Conversion rates
* Cost efficiency
* Process efficiency
* Business goals
* Success metrics

## Next Steps

* Learn about [Security](/guides/notifyer-system/enterprise/security)
* Explore [Scaling](/guides/notifyer-system/enterprise/scaling)
* Check out our [API Reference](/api-reference/notifier-system)
* Read our [Getting Started](/guides/notifyer-system/getting-started) guide


# Enterprise Scaling
Source: https://docs.whatsable.app/guides/notifyer-system/enterprise/scaling

Learn how to scale your WhatsApp messaging with Notifyer System

# Enterprise Scaling

Notifyer System provides robust scaling capabilities for enterprise-level WhatsApp messaging.

## Scaling Features

### Infrastructure

* Auto-scaling
* Load balancing
* High availability
* Geographic distribution
* Disaster recovery
* Backup systems
* Monitoring

### Performance

* Message queuing
* Priority queuing
* Rate limiting
* Caching
* CDN integration
* Database optimization
* Resource management

### Capacity

* Unlimited messages
* Multiple channels
* Concurrent processing
* Batch processing
* Bulk messaging
* Scheduled messages
* Message routing

## Scaling Implementation

### Message Queue

```javascript theme={null}
// Example: Implementing message queuing
const queueMessage = async (message) => {
  try {
    const queueItem = {
      message,
      priority: message.metadata?.priority || 'normal',
      timestamp: new Date(),
      retryCount: 0
    };

    await messageQueue.add(queueItem, {
      priority: getPriorityWeight(queueItem.priority),
      attempts: 3,
      backoff: {
        type: 'exponential',
        delay: 1000
      }
    });
  } catch (error) {
    console.error('Error queueing message:', error);
    throw error;
  }
};
```

### Load Balancing

```javascript theme={null}
// Example: Load balanced API call
const sendScaledMessage = async (message) => {
  try {
    const response = await axios.post(
      'https://api.notifiersystem.com/v1/messages',
      message,
      {
        headers: {
          'Authorization': `Bearer ${process.env.NOTIFIER_SYSTEM_API_KEY}`,
          'Content-Type': 'application/json',
          'X-Tenant-ID': process.env.TENANT_ID,
          'X-Load-Balancer-Key': generateLoadBalancerKey()
        }
      }
    );
    return response.data;
  } catch (error) {
    console.error('Error sending message:', error);
    throw error;
  }
};
```

## Best Practices

### Infrastructure

* Monitor system resources
* Set up auto-scaling
* Implement load balancing
* Use CDN for media
* Optimize database
* Regular maintenance
* Backup strategy

### Performance

* Implement caching
* Use message queues
* Optimize API calls
* Monitor response times
* Handle rate limits
* Error handling
* Retry logic

### Capacity Planning

* Monitor usage
* Set up alerts
* Plan for growth
* Resource allocation
* Cost optimization
* Performance testing
* Load testing

## Monitoring

### System Monitoring

* Resource usage
* Performance metrics
* Error rates
* Response times
* Queue lengths
* Cache hit rates
* Database performance

### Business Metrics

* Message volume
* Success rates
* Response rates
* Cost per message
* User engagement
* ROI metrics
* Growth metrics

## Next Steps

* Learn about [Security](/guides/notifyer-system/enterprise/security)
* Explore [Customization](/guides/notifyer-system/enterprise/customization)
* Check out our [API Reference](/api-reference/notifier-system)
* Read our [Getting Started](/guides/notifyer-system/getting-started) guide


# Enterprise Security
Source: https://docs.whatsable.app/guides/notifyer-system/enterprise/security

Learn about enterprise-grade security features in Notifyer System

# Enterprise Security

Notifyer System provides comprehensive security features for enterprise-level WhatsApp messaging.

## Security Features

### Authentication

* API key authentication
* OAuth 2.0 support
* Two-factor authentication
* Role-based access control
* Session management
* IP whitelisting
* API key rotation

### Data Protection

* End-to-end encryption
* Data encryption at rest
* Secure data transmission
* Data backup
* Data retention policies
* Data access controls
* Audit logging

### Compliance

* GDPR compliance
* CCPA compliance
* HIPAA compliance
* SOC 2 compliance
* ISO 27001 compliance
* Regular security audits
* Compliance reporting

## Security Implementation

### API Security

```javascript theme={null}
// Example: Secure API call with multiple security headers
const sendSecureMessage = async (message) => {
  try {
    const response = await axios.post(
      'https://api.notifiersystem.com/v1/messages',
      message,
      {
        headers: {
          'Authorization': `Bearer ${process.env.NOTIFIER_SYSTEM_API_KEY}`,
          'Content-Type': 'application/json',
          'X-Tenant-ID': process.env.TENANT_ID,
          'X-Request-ID': uuidv4(),
          'X-Security-Token': await generateSecurityToken()
        }
      }
    );
    return response.data;
  } catch (error) {
    console.error('Error sending message:', error);
    throw error;
  }
};
```

### Webhook Security

```javascript theme={null}
// Example: Secure webhook endpoint
app.post('/webhook/message-status', 
  validateWebhookSignature,
  rateLimit,
  async (req, res) => {
    const { message_id, status, timestamp } = req.body;
    
    await updateMessageStatus({
      message_id,
      status,
      timestamp,
      security: {
        ip_address: req.ip,
        user_agent: req.headers['user-agent'],
        request_id: req.headers['x-request-id']
      }
    });
});
```

## Best Practices

### Security Measures

* Regular security audits
* Penetration testing
* Vulnerability scanning
* Security monitoring
* Incident response
* Security training
* Documentation

### Access Control

* Role-based access
* Least privilege principle
* Access logging
* Access reviews
* Access revocation
* Session management
* Password policies

### Data Protection

* Data classification
* Data encryption
* Data backup
* Data retention
* Data disposal
* Data access logs
* Data breach response

## Monitoring

### Security Monitoring

* Real-time alerts
* Security logs
* Access logs
* Error logs
* Performance metrics
* Compliance reports
* Security dashboards

### Incident Response

* Incident detection
* Incident investigation
* Incident containment
* Incident resolution
* Incident reporting
* Post-incident review
* Documentation

## Next Steps

* Learn about [Scaling](/guides/notifyer-system/enterprise/scaling)
* Explore [Customization](/guides/notifyer-system/enterprise/customization)
* Check out our [API Reference](/api-reference/notifier-system)
* Read our [Getting Started](/guides/notifyer-system/getting-started) guide


# Notifyer System Features
Source: https://docs.whatsable.app/guides/notifyer-system/features

Explore the enterprise features of Notifyer System

# Notifyer System Features

Notifyer System provides comprehensive enterprise-grade features for WhatsApp messaging.

## Core Features

### Message Types

* Text messages
* Media messages (images, documents, audio, video)
* Location sharing
* Contact sharing
* Interactive messages
* List messages
* Button messages
* Product messages
* Order messages

### Message Management

* Message status tracking
* Delivery receipts
* Read receipts
* Message history
* Message templates
* Bulk messaging
* Scheduled messages
* Priority queuing
* Message routing

### Security

* End-to-end encryption
* API key authentication
* Rate limiting
* IP whitelisting
* Two-factor authentication
* Audit logs
* Data encryption at rest
* Compliance monitoring

## Enterprise Features

### Multi-tenant Support

* Multiple business units
* Separate message queues
* Custom branding
* Independent analytics
* Role-based access

### Advanced Templates

* Pre-approved message templates
* Dynamic variables
* Multi-language support
* Template analytics
* Template versioning
* Template approval workflow
* Template categories

### Automation

* Workflow automation
* Conditional messaging
* Event-based triggers
* Custom webhooks
* Integration with third-party services
* Business rules engine
* Custom scripting

### Analytics

* Message delivery rates
* Response times
* User engagement
* Template performance
* Custom reports
* Real-time dashboards
* Export capabilities
* API access

## Best Practices

### Enterprise Setup

* Define clear workflows
* Set up proper monitoring
* Implement security measures
* Configure backup systems
* Document processes

### Message Strategy

* Use approved templates
* Implement proper error handling
* Monitor message status
* Follow WhatsApp guidelines
* Regular template updates
* A/B testing
* Performance optimization

## Next Steps

* Learn about [Integrations](/guides/notifyer-system/integrations)
* Explore [Enterprise Features](/guides/notifyer-system/enterprise/security)
* Check out our [API Reference](/api-reference/notifier-system)
* Read our [Getting Started](/guides/notifyer-system/getting-started) guide


# Getting Started with Notifyer System
Source: https://docs.whatsable.app/guides/notifyer-system/getting-started

Learn how to get started with Notifyer System, the flagship WhatsApp messaging solution

# Getting Started with Notifyer System

Notifyer System is our flagship WhatsApp messaging solution, designed for enterprise-level communication needs.

## Prerequisites

* WhatsApp Business API account
* Business verification
* Technical team for integration
* Understanding of enterprise messaging
* Your Notifyer System API credentials

## Quick Setup

1. Contact our sales team for enterprise setup
2. Complete business verification
3. Set up your WhatsApp Business API account
4. Configure your Notifyer System instance
5. Get your API credentials
6. Set up webhooks and monitoring

## First Message

Here's a quick example of sending your first message:

```bash theme={null}
curl -X POST https://api.notifiersystem.com/v1/messages \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+1234567890",
    "template": "enterprise_welcome",
    "variables": {
      "name": "John",
      "company": "Enterprise Corp",
      "department": "Sales"
    },
    "metadata": {
      "campaign_id": "welcome_2024",
      "segment": "enterprise",
      "priority": "high"
    }
  }'
```

## Enterprise Features

* Multi-tenant support
* Role-based access control
* Advanced security features
* Custom integrations
* Enterprise-grade support

## Next Steps

* Learn about [Features](/guides/notifyer-system/features)
* Explore [Integrations](/guides/notifyer-system/integrations)
* Check out [Enterprise Features](/guides/notifyer-system/enterprise/security)
* Review our [API Reference](/api-reference/notifier-system)


# Notifyer System Integrations
Source: https://docs.whatsable.app/guides/notifyer-system/integrations

Learn how to integrate Notifyer System with your enterprise applications

# Notifyer System Integrations

Integrate Notifyer System with your enterprise tools and platforms.

## Available Integrations

### Enterprise Platforms

* Salesforce
* SAP
* Oracle
* Microsoft Dynamics
* ServiceNow

### CRM Systems

* Salesforce
* HubSpot
* Zoho CRM
* Pipedrive
* Microsoft Dynamics
* Custom CRM solutions

### E-commerce Platforms

* Shopify Plus
* Magento Enterprise
* SAP Commerce
* Oracle Commerce
* Custom e-commerce solutions

### Marketing Tools

* Adobe Marketing Cloud
* Salesforce Marketing Cloud
* Oracle Marketing Cloud
* HubSpot Enterprise
* Custom marketing platforms

## Custom Integration

### REST API

```javascript theme={null}
const axios = require('axios');

const sendEnterpriseMessage = async (message) => {
  try {
    const response = await axios.post(
      'https://api.notifiersystem.com/v1/messages',
      message,
      {
        headers: {
          'Authorization': `Bearer ${process.env.NOTIFIER_SYSTEM_API_KEY}`,
          'Content-Type': 'application/json',
          'X-Tenant-ID': process.env.TENANT_ID
        }
      }
    );
    return response.data;
  } catch (error) {
    console.error('Error sending message:', error);
    throw error;
  }
};
```

### Webhooks

Configure webhooks for enterprise-level monitoring:

```json theme={null}
{
  "event": "message.status",
  "data": {
    "message_id": "msg_123",
    "status": "delivered",
    "template": "enterprise_welcome",
    "variables": {
      "name": "John",
      "company": "Enterprise Corp",
      "department": "Sales"
    },
    "metadata": {
      "campaign_id": "welcome_2024",
      "segment": "enterprise",
      "priority": "high"
    },
    "timestamp": "2024-03-20T10:00:00Z"
  }
}
```

## Enterprise Features

### Multi-tenant Support

* Separate API keys per tenant
* Custom webhook endpoints
* Tenant-specific templates
* Independent analytics
* Custom branding

### Security

* IP whitelisting
* API key rotation
* Audit logging
* Data encryption
* Compliance monitoring

### Monitoring

* Real-time status
* Error tracking
* Performance metrics
* Usage analytics
* Cost tracking

## Best Practices

### Integration

* Use environment variables
* Implement retry logic
* Handle rate limits
* Monitor webhook delivery
* Use template variables
* Implement proper error handling
* Set up monitoring
* Regular security audits

### Development

* Follow API guidelines
* Use SDK when available
* Test thoroughly
* Document integration
* Version control
* CI/CD pipeline
* Regular updates

## Next Steps

* Read our [Getting Started](/guides/notifyer-system/getting-started) guide
* Explore [Features](/guides/notifyer-system/features)
* Check out [Enterprise Features](/guides/notifyer-system/enterprise/security)
* Review our [API Reference](/api-reference/notifier-system)


# What Make modules and fields does Whatsable expose?
Source: https://docs.whatsable.app/guides/notifyer-system/make-fields

Every Whatsable Make module and field: Incoming and Incoming & Outgoing triggers, Send, Schedule a follow-up, Update a Contact, and Get delivery status.

This page is the **field dictionary** for the Whatsable for WhatsApp Business app on Make — every unlocked trigger, action, and search module input/output you can map in a scenario. Use it when you already know you want Make and need exact labels, types, and requiredness.

For connect steps, coexistence walkthrough, examples, and troubleshooting, use [Make overview](/guides/notifyer-system/make-overview).

## Prerequisites

* **Plan:** Make requires **Pro** or **Agency** (Bulk Message does not include integrations).
* **WhatsApp number:** Connected in Whatsable. Coexistence is supported — keep the WhatsApp Business app; phone replies can fire the dual-direction trigger.
* **Make app:** Public marketplace listing **Whatsable for WhatsApp Business** ([make.com/en/integrations/whatsable-message](https://www.make.com/en/integrations/whatsable-message)). Search **Whatsable** in the Make scenario editor.
* **API key:** From the Whatsable console API Keys page. Create a **Notifyer only** connection in Make and paste that key (core product key — not a Meta Graph token).

<Info>
  Install via the Whatsable console **Connect to Make** flow or the public Make listing. You need Admin, Owner, or App Developer role in your Make organization to install apps.
</Info>

***

## At a glance

| Kind | Exact name in Make |
| - | - |
| Trigger (instant) | **Incoming Messages from console (Notifyer System)** |
| Trigger (instant) | **Incoming & Outgoing Messages from console (Notifyer System)** |
| Action | **Send WhatsApp Message** |
| Action | **Schedule a follow-up Message** |
| Action | **Update a Contact** |
| Search | **Get delivery status of a message** |

All modules use the Whatsable for WhatsApp Business app and a Notifyer API key connection.

***

## Trigger: Incoming Messages from console (Notifyer System)

**Type:** Instant · **Connection:** Notifyer only

Fires every time an incoming message arrives in your Whatsable console. Full-featured trigger for AI chatbot workflows, lead qualification, CRM updates, and real-time automations — includes AI note, conversation history, and scheduling data.

### Configure inputs

<ResponseField name="Webhook" type="webhook">
  Create or select a Make webhook bound to your Notifyer only connection (API key).
</ResponseField>

### Output fields — contact identity

<ResponseField name="phone_number" type="text / number">
  The contact’s phone number (for example `14155550187`). May arrive as a number rather than a string.
</ResponseField>

<ResponseField name="user_id" type="text">
  Unique internal ID for this contact (UUID).
</ResponseField>

<ResponseField name="recipient_name" type="text">
  Display name used by the AI to address this contact.
</ResponseField>

<ResponseField name="labels" type="text">
  Comma-separated labels on the conversation (for example `Hot Lead, Buyer Qualified`).
</ResponseField>

### Output fields — message data

<ResponseField name="message_type" type="text">
  Documented values: `text`, `audio`, `image`, or `document`.
</ResponseField>

<ResponseField name="incoming_message" type="boolean">
  `true` for this trigger — confirms an inbound message from the contact.
</ResponseField>

<ResponseField name="send_by" type="text">
  Empty on this incoming-only trigger. On the dual-direction trigger, identifies the sending system or teammate.
</ResponseField>

<ResponseField name="was_message_by_human" type="boolean">
  `true` when a person sent the message.
</ResponseField>

<ResponseField name="attachment_url" type="text">
  Public URL of any attached file, or empty when there is none.
</ResponseField>

<ResponseField name="is_scheduled" type="boolean">
  `true` when this event is a scheduled delivery; `false` for real-time messages.
</ResponseField>

<ResponseField name="referral" type="object">
  Present when the inbound message came from a Click-to-WhatsApp ad or post. Typically on the **first** inbound after the tap; later messages usually omit it. Nested keys:

  | Key | Meaning |
  | - | - |
  | `source_type` | `"ad"` or `"post"` |
  | `source_id` | Ad or post ID |
  | `source_url` | Where they tapped |
  | `headline` / `body` | Ad copy |
  | `media_type` | `"image"` or `"video"` |
  | `image_url` / `video_url` | Creative URLs |
  | `ctwa_clid` | Click ID for Meta Conversions API |

  Persist `ctwa_clid` and `source_id` as soon as you see them. See also [Incoming message — Click-to-WhatsApp ads](/guides/notifyer-system/api/incoming-message#click-to-whatsapp-ads).
</ResponseField>

### Output fields — conversation history

<ResponseField name="last_messages" type="text">
  JSON string (or array representation) of recent messages. Each item includes `type` (`user` / `bot`), `content`, `timestamp`, and `content_type`. Parse before iterating.
</ResponseField>

<ResponseField name="last_message_of_user" type="text">
  The most recent message from the contact — the message that triggered this run.
</ResponseField>

<ResponseField name="last_message_of_bot" type="text">
  The most recent message your business sent (human or automation).
</ResponseField>

<ResponseField name="user_last_message_time" type="number">
  Unix timestamp (milliseconds) of the contact’s last message.
</ResponseField>

<ResponseField name="bot_last_message_time" type="number">
  Unix timestamp (milliseconds) of your business’s last message to this contact.
</ResponseField>

<ResponseField name="conversation_paragraph" type="text">
  Flat, readable conversation history — useful for LLM prompts without parsing `last_messages`.
</ResponseField>

### Output fields — AI context and automation

<ResponseField name="note" type="text">
  AI context note stored on this contact. Update it with **Update a Contact**.
</ResponseField>

<ResponseField name="note_automation" type="text">
  Automation instructions for the AI based on conversation events.
</ResponseField>

<ResponseField name="scheduled_messages" type="text">
  Description of messages currently scheduled to this contact. **Available on this Incoming-only trigger** — not on the Incoming & Outgoing trigger.
</ResponseField>

***

## Trigger: Incoming & Outgoing Messages from console (Notifyer System)

**Type:** Instant · **Connection:** Notifyer only

Fires on both incoming and outgoing messages — every message sent or received in your Whatsable console, including replies typed in the WhatsApp Business app. Use it for conversation logging, CRM sync, or automations that must react when a teammate replies on their phone.

Description in Make: "Get your sent and incoming messages data through a single webhook."

### Configure inputs

Same webhook + Notifyer only connection setup as the Incoming-only trigger.

### Output fields

Identical to **Incoming Messages from console** above, with these differences:

<ResponseField name="incoming_message" type="boolean">
  `true` when the contact sent a message; `false` when your business sent a message. Add a Router or Filter after this trigger to branch by direction.
</ResponseField>

<ResponseField name="send_by" type="text">
  On outgoing messages: `"WhatsApp App"` (phone app), a teammate’s name (inbox), or an automation/app name (Make, Zapier, n8n, API, bot). Empty or omitted on incoming messages.
</ResponseField>

<ResponseField name="was_message_by_human" type="boolean">
  `true` when a person sent the message (phone app or inbox); `false` when a bot or automation sent it.
</ResponseField>

<Warning>
  The `scheduled_messages` field is only available on the **Incoming Messages from console** trigger — not on this dual-direction trigger.
</Warning>

<Tip>
  Use a Make Filter or Router on `incoming_message`, `send_by`, and `was_message_by_human` to split incoming vs outgoing and human phone-app replies vs automations.
</Tip>

***

## Action: Send WhatsApp Message

**Connection:** Notifyer only

Sends a WhatsApp message using the official WhatsApp API. You can add labels and write notes that appear in Whatsable’s chat interface. Choose **Configuration**: template (start a conversation / proactive) or non-template (inside the customer service window).

### Mode A — Send WhatsApp Template (to start conversation)

Use this to initiate a new conversation or reach out proactively. Requires a Meta-approved template.

<ResponseField name="Phone Number" type="text">
  Recipient in international format — digits only, no `+` or spaces (for example `14155550187`).
</ResponseField>

<ResponseField name="Template" type="dropdown">
  Select from your approved templates. The dropdown shows a live preview of body, language, and category.
</ResponseField>

<ResponseField name="Body 1, Body 2, … (variables)" type="text">
  One field per template variable (`{{1}}`, `{{2}}`, …). Required when the template has variables.
</ResponseField>

<ResponseField name="Media URL" type="text">
  Public URL for a media header (image, video, or document). Only when the selected template has a media header.
</ResponseField>

<ResponseField name="Visit Website URL / dynamic URL button" type="text">
  Full URL including the dynamic portion, when the template has a dynamic URL button.
</ResponseField>

<ResponseField name="Note" type="text">
  AI context about this contact. Stored on the contact — **not** sent to the recipient.
</ResponseField>

<ResponseField name="Labels" type="multiselect">
  Labels to apply to this conversation. Labels appear in your Whatsable console.
</ResponseField>

### Mode B — Non-template message (person must write to you first)

Only inside Meta’s customer service window after the contact’s last inbound message. Outside that window, use an approved template.

<ResponseField name="Phone Number" type="text">
  Same digit format as Phone Number above.
</ResponseField>

<ResponseField name="Message Type" type="dropdown">
  **Text Message**, **Image Message**, **Video Message**, **Document Message**, or **Audio Message**. Nested fields:

  | Message Type | Nested fields |
  | - | - |
  | Text Message | **Message Content** (text, required); **Enable Link Preview** (boolean, optional, default false) |
  | Image Message | **Image URL** (url, required); **Caption** (text, optional) |
  | Video Message | **Video URL** (url, required); **Caption** (text, optional) |
  | Document Message | **Document URL** (url, required); **Caption** (text, optional); **Filename** (text) |
  | Audio Message | **Audio URL** (url, required) |
</ResponseField>

<ResponseField name="Labels" type="multiselect">
  Labels to apply to this conversation.
</ResponseField>

<ResponseField name="Note" type="text">
  AI context note for this contact.
</ResponseField>

<Warning>
  Testing this action sends a **real** WhatsApp message. Use a personal test number during setup.
</Warning>

***

## Action: Schedule a follow-up Message

**Connection:** Notifyer only

Schedules a WhatsApp message for later, with optional reply and label conditions so it can cancel or skip when the lead is already engaged.

Message fields are the same as **Send WhatsApp Message** (template or non-template, including phone, template/variables or message type, Note, and labels), **plus** the schedule and condition fields below.

### When to send — Relative (delay from now)

<ResponseField name="Delay Value" type="select">
  Choose only: **1, 2, 3, 4, 5, 10, 15, 20, 30, 60, 90, or 120**.
</ResponseField>

<ResponseField name="Delay Unit" type="select">
  **Minutes**, **Hours**, or **Days**.
</ResponseField>

### When to send — Specific date and time

<ResponseField name="Date & Time" type="datetime">
  Exact send time.
</ResponseField>

<ResponseField name="Timezone" type="select">
  Timezone for the scheduled time (full global list in Make — GMT-11 through GMT+12).
</ResponseField>

### Reply Condition

Optional but recommended. Cancels the scheduled send if the contact replies within the chosen rule.

| Condition label |
| - |
| Recipient did not reply after my last message *(recommended default)* |
| Recipient never replied to any of my messages |
| Recipient did not reply within 20 minutes |
| Recipient did not reply within 45 minutes |
| Recipient did not reply within 3 hours |
| Recipient did not reply within 6 hours |
| Recipient did not reply within 12 hours |
| Recipient did not reply within 24 hours |
| Recipient did not reply within 48 hours |
| Recipient did not reply within 72 hours |

### Label condition (optional)

<ResponseField name="Label Condition" type="select">
  **Include** — only send if the contact has this label at send time. **Does Not Include** — only send if they do not.
</ResponseField>

<ResponseField name="Label" type="select">
  Label evaluated when the scheduled send time arrives.
</ResponseField>

Scheduled messages are visible in the Whatsable console under the contact’s conversation — you can view or cancel them there.

<Warning>
  This is **not** a native drip builder inside Whatsable. Day-0 / day-3 / day-6 sequences are multiple Make modules (or routers) that each schedule one message. Whatsable sends each scheduled message; the sequence logic lives in Make.
</Warning>

***

## Action: Update a Contact

**Connection:** Notifyer only

Updates a contact in Whatsable — display name, AI note, and labels. The Make action description also states you can **assign the conversation to a teammate**.

### Documented fields

<ResponseField name="Phone Number" type="text">
  Lookup key in international digit format. Creates a contact if none exists yet.
</ResponseField>

<ResponseField name="Display Name" type="text">
  Display name in the Whatsable chat interface.
</ResponseField>

<ResponseField name="Note" type="text">
  AI context note for this contact (name, email, preferences, language, and so on).
</ResponseField>

<ResponseField name="Add Labels" type="multiselect">
  Labels to add. Whatsable conversation labels are the source of truth inside Whatsable.
</ResponseField>

<ResponseField name="Remove Labels" type="multiselect">
  Labels to remove. **Remove All** clears every label on this contact.
</ResponseField>

<Info>
  **Assign a teammate:** Update a Contact can assign the conversation to a teammate (Make action description + Zapier / Make / API). Documented fields on this page today are Phone Number, Display Name, Note, and Add/Remove Labels. Confirm any assignee control in your live Make module sample — do not rely on an undocumented field name. Operator how-to: [Chat assignment](/guides/notifyer-system/chat-assignment) and [Team inbox](/guides/notifyer-system/team-inbox).
</Info>

***

## Search: Get delivery status of a message

**Connection:** Notifyer only

Checks whether a previously sent WhatsApp message was delivered — useful for fallback paths (for example email) when a number may be wrong or inactive.

<ResponseField name="Message ID" type="text">
  Map from the output of a prior **Send WhatsApp Message** or **Schedule a follow-up Message** module in the same scenario.
</ResponseField>

Connect a Router after this search to handle delivered vs not-delivered paths (for example send a fallback Gmail or Outlook email).

<Note>
  If a lookup fails in scenario history, re-check the mapped Message ID and contact support if needed. Do not assume every Message ID always resolves in every environment.
</Note>

***

## Limits and what this does NOT do

<Warning>
  **No native drip builder.** Multi-day sequences use Make (or Zapier / n8n) schedule modules plus reply conditions — not a built-in drip product inside Whatsable.
</Warning>

<Warning>
  **No CRM ↔ Whatsable bidirectional label mirror.** Add/Remove labels update Whatsable conversation labels. They do not sync Monday/Pipedrive (or other) CRM tags as one shared store.
</Warning>

<Warning>
  **Coexistence:** Do **not** uninstall the WhatsApp Business app to “enable” API or Make. Keep using the phone; those replies can still start scenarios via the Incoming & Outgoing trigger.
</Warning>

* **Bulk Message** plan: no Make / integrations — upgrade to Pro or Agency.
* **Non-template** sends only inside the customer service window after the contact’s last inbound; otherwise use a template.
* **Phone format:** digits only, full international, no `+`, spaces, or dashes.
* **Group Messaging** is **unavailable** as a product add-on and is **not** a documented Make module on this fields page.
* Do not invent trigger `message_type` values beyond `text`, `audio`, `image`, and `document`.
* Typing-indicator dots are not a documented Whatsable automation claim.
* Do not invent location or sticker send types on Make modules.

***

## Related features and next steps

<CardGroup>
  <Card title="Make overview" icon="diagram-project" href="/guides/notifyer-system/make-overview">
    Connect, coexistence, examples, troubleshooting
  </Card>

  <Card title="Zapier fields" icon="bolt" href="/guides/notifyer-system/zapier-fields">
    Parallel Zapier trigger/action field dictionary
  </Card>

  <Card title="Team inbox" icon="inbox" href="/guides/notifyer-system/team-inbox">
    Shared inbox and human replies alongside automations
  </Card>

  <Card title="Chat assignment" icon="user-check" href="/guides/notifyer-system/chat-assignment">
    Assign chats via Make, Zapier, API, keywords, or AI
  </Card>
</CardGroup>

Also: [Incoming message / CTWA](/guides/notifyer-system/api/incoming-message) · [n8n overview](/guides/notifyer-system/n8n-overview) · [Plans](/guides/notifyer-system/plans-bulk-message-pro-agency).

***

## FAQ

### Does the Make trigger fire when someone replies in the WhatsApp Business app?

Yes, when coexistence is enabled and you use **Incoming & Outgoing Messages from console**. Filter on `incoming_message` (`false`), `send_by` (for example `"WhatsApp App"`), and `was_message_by_human`.

### Which trigger should I use for AI chatbot scenarios?

Prefer **Incoming Messages from console** when you only need inbound events and want `scheduled_messages` in the payload. Use the dual-direction trigger when you must also react to outgoing phone-app or inbox replies.

### Can I build day-0 / day-3 / day-6 WhatsApp drips with Whatsable and Make?

Yes, by chaining **Schedule a follow-up Message** modules (and reply conditions) in Make. Whatsable is not a native drip builder — the sequence logic lives in Make.

### Does Bulk Message include Make?

No. Make and other integrations require **Pro** or **Agency**.

### Which fields does Update a Contact document today?

**Phone Number**, **Display Name**, **Note**, **Add Labels**, and **Remove Labels**. Assigning a teammate is supported as a product capability via Make; confirm the live module for any assignee control rather than inventing a field name.


# Make
Source: https://docs.whatsable.app/guides/notifyer-system/make-overview

Notifyer System modules in Make — triggers for incoming and outgoing WhatsApp messages (including the WhatsApp Business app), actions, and search. Coexistence is supported.

# Notifyer System Integration with Make

<Frame>
  <img />
</Frame>

<Tip>
  This guide covers every module available for the Notifyer System inside Make — including all triggers, actions, and the search module — so you can build fully automated WhatsApp workflows.
</Tip>

<Info>
  **Meta WhatsApp Coexistence is supported on Notifyer System.** You do **not** need to delete the WhatsApp Business app or stop using the number on your phone. After Embedded Signup, the same number works in the WhatsApp Business app, the Notifyer chat inbox, and automations (Make, Zapier, n8n, API, and webhooks) at the same time.
</Info>

## Available modules at a glance

The Notifyer System is part of the **Whatsable for WhatsApp Business** app on Make. Once installed, you get access to the following modules using your Notifyer API key:

<CardGroup>
  <Card title="Triggers (Instant)" icon="bolt">
    * Incoming Messages from console (Notifyer System)
    * Incoming & Outgoing Messages from console (Notifyer System)
  </Card>

  <Card title="Actions" icon="play">
    * Send WhatsApp Message
    * Schedule a follow-up Message
    * Update a Contact
  </Card>

  <Card title="Search" icon="magnifying-glass">
    * Get delivery status of a message
  </Card>
</CardGroup>

<Info>
  All modules in this guide are part of the **Whatsable for WhatsApp Business** app on Make. Notifyer System users connect using their **Notifyer API key**.
</Info>

***

## Prerequisites

Before getting started, make sure you have:

<CardGroup>
  <Card title="Notifyer System Account" icon="user">
    Active Notifyer System account with a subscription plan (Monthly or Pay-as-you-go) and a connected WhatsApp number
  </Card>

  <Card title="Make Account" icon="user">
    Access to [Make](https://www.make.com/en/register) workflow automation platform
  </Card>
</CardGroup>

<Tip>
  New to Notifyer System? [Sign up here](https://console.notifyer-systems.com/)
</Tip>

***

## Setting up your Notifyer System account

<Steps>
  <Step title="Complete the Embedding Process">
    Before sending WhatsApp messages, complete the [embedding process](/guides/notifyer-system/embedding-process), which connects your WhatsApp Business account to Notifyer System. You do **not** need to delete the WhatsApp Business app — [coexistence](/guides/notifyer-system/embedding-process#whatsapp-coexistence) is supported.

    <Info>
      The embedding process is required by Meta to ensure proper business verification and compliance with WhatsApp Business Platform policies.
    </Info>
  </Step>

  <Step title="Set up message templates (if using template messages)">
    WhatsApp templates are pre-approved message formats required to initiate a new conversation with a contact. Create and get them approved in Notifyer before using them in Make.

    <Accordion title="How to create a template">
      <Steps>
        <Step title="Navigate to Templates">
          Go to **Your Templates** in your Notifyer dashboard
        </Step>

        <Step title="Create Template">
          Click the **Create Template** tab at the top of the page
        </Step>

        <Step title="Fill out the form">
          <ResponseField name="Template Name" type="string">
            Choose a descriptive name for internal reference
          </ResponseField>

          <ResponseField name="Language" type="string">
            Choose your template's primary language
          </ResponseField>

          <ResponseField name="Category" type="string">
            Select the appropriate message category (Marketing, Utility, Authentication)
          </ResponseField>

          <ResponseField name="Header" type="image | document | video">
            Optional: Add an image, document, or video header
          </ResponseField>

          <ResponseField name="Message Body" type="string">
            Craft your message content. Use `{{1}}`, `{{2}}` placeholders for dynamic variables
          </ResponseField>

          <ResponseField name="Buttons" type="button">
            Optional: Configure call-to-action or quick reply buttons
          </ResponseField>
        </Step>

        <Step title="Submit for review">
          Click **Preview and Submit**
        </Step>
      </Steps>

      <Warning>
        Templates are typically reviewed within 24 hours. Utility and Authentication templates have the highest approval rates.
      </Warning>
    </Accordion>
  </Step>

  <Step title="Get your Notifyer API key">
    1. In your Notifyer dashboard, navigate to [**API Keys**](https://console.notifyer-systems.com/api-key)
    2. Copy your unique API key
    3. Store it securely — you will need it when creating the Make connection

    <Warning>
      Never share your API key publicly or commit it to version control systems.
    </Warning>
  </Step>
</Steps>

***

## Connect Notifyer System to Make

<Steps>
  <Step title="Install the app in Make">
    1. Log in to your Make account
    2. Navigate to your Notifyer System dashboard and select **Connect to Make** in the side menu
    3. Click **Continue** in the connection guide popup
    4. Click **Install**, select your Make organization at the bottom of the screen, then click **Install** again

    <Note>
      You need Admin, Owner, or App Developer role in your Make organization to install apps.
    </Note>

    <Check>
      The **Whatsable for WhatsApp Business** app is now installed and ready to use in your Make scenarios
    </Check>
  </Step>

  <Step title="Create a new Make scenario">
    1. Log in to your Make account at [make.com](https://www.make.com)
    2. Click **+ Create a new scenario**
    3. You are now ready to add your first module — follow the trigger setup guide in the [Module Reference](#setting-up-a-notifyer-trigger-in-make) section below
  </Step>
</Steps>

***

## Module Reference

### Triggers

Instant triggers fire in real time whenever a qualifying event occurs in your Notifyer console. Both triggers below use the **Whatsable for WhatsApp Business** app in Make and require a webhook plus your Notifyer API key connection.

<Info>
  Both triggers are **Instant** — they fire immediately when a message event occurs in your Notifyer console.
</Info>

***

### Setting up a Notifyer trigger in Make

Both Notifyer triggers follow the same 5-step setup in Make. The only difference is which trigger you select in Step 1.

<Steps>
  <Step title="Step 1 — Select your trigger">
    1. In your scenario, click the large **+** button to add a module
    2. Search for **Whatsable** or **Whatsable for WhatsApp Business**
    3. Open the **Whatsable for WhatsApp Business** app
    4. Under **Triggers**, select the trigger you need:

    | Trigger | When to use it |
    | - | - |
    | **Incoming Messages from console (Notifyer System)** | Fires only when a contact sends your business a message |
    | **Incoming & Outgoing Messages from console (Notifyer System)** | Fires on every message — both incoming and outgoing, including replies typed in the WhatsApp Business app |
  </Step>

  <Step title="Step 2 — Create a webhook">
    After selecting the trigger, the module configuration window opens. The first required field is **Webhook**.

    1. Click the **Add** button next to the **Webhook** dropdown (the dropdown will show "Choose a hook..." if no webhook exists yet)
    2. This opens the **Create a webhook** dialog
  </Step>

  <Step title="Step 3 — Name your webhook and set up a connection">
    In the **Create a webhook** dialog:

    1. Enter a **Webhook name** — use something descriptive so you can identify it later (e.g. `My Notifyer Systems webhook`)
    2. Under **Connection**, either:
       * Select an existing connection if you have already connected Notifyer to Make before, **or**
       * Click **Add** next to the Connection dropdown to create a new connection (continue to Step 4)
    3. If you already have a connection selected, click **Save** to create the webhook and skip to Step 5
  </Step>

  <Step title="Step 4 — Create your Notifyer connection (first time only)">
    If you clicked **Add** in Step 3, the **Create a connection** dialog opens on top of the webhook dialog.

    1. Enter a **Connection name** (e.g. `My Notifyer only connection`)
    2. Paste your **Notifyer API key** in the **API Key** field — get this from your [Notifyer API Keys page](https://console.notifyer-systems.com/api-key)
    3. Click **Save**

    Make validates your API key automatically. Once saved, you return to the **Create a webhook** dialog with your new connection selected.

    <Info>
      You only need to create this connection once. All future Notifyer modules in Make can reuse the same saved connection.
    </Info>

    Back in the **Create a webhook** dialog, click **Save** to finish creating the webhook.
  </Step>

  <Step title="Step 5 — Save the trigger and activate your scenario">
    You are now back in the main module configuration window. The webhook you created is selected and a **Webhook URL** is displayed (e.g. `https://hook.eu1.make.com/...`).

    1. Confirm your webhook is selected in the **Webhook** dropdown
    2. Click **Save** to finish configuring the trigger module
    3. Toggle your scenario to **Active** (or click **Run once** to test first)

    <Check>
      Your trigger is now live. When a matching message event occurs in your Notifyer console, Make will run your scenario automatically.
    </Check>

    <Tip>
      Set the scenario schedule to **Immediately as data arrives** (shown in the bottom toolbar) so instant triggers fire without delay.
    </Tip>
  </Step>
</Steps>

***

#### Incoming Messages from console (Notifyer System)

<Info>
  **Type:** Instant Trigger | **Connection:** Notifyer only
</Info>

Fires every time an **incoming message** arrives in your Notifyer console. This is the full-featured trigger for building AI chatbot workflows, lead qualification, CRM updates, and real-time automations — it exposes all conversation context fields including the AI note, conversation history, and scheduling data.

**Description in Make:** *"Incoming Messages from console (Notifyer System)"*

**How to set up:** Follow the [5-step trigger setup guide](#setting-up-a-notifyer-trigger-in-make) above. In Step 1, select **Incoming Messages from console (Notifyer System)** from the Triggers list.

**Output fields — everything your scenario receives when triggered:**

<AccordionGroup>
  <Accordion title="Contact identity">
    <ResponseField name="phone_number" type="text">
      The phone number of the person who sent the message (e.g. `14155550187`)
    </ResponseField>

    <ResponseField name="user_id" type="text">
      Unique internal ID for this contact in Notifyer (UUID format)
    </ResponseField>

    <ResponseField name="recipient_name" type="text">
      The first name or display name used by the AI to address this contact in conversation
    </ResponseField>

    <ResponseField name="labels" type="text">
      Comma-separated list of labels currently applied to this conversation (e.g. `Hot Lead, Buyer Qualified, Urgent`)
    </ResponseField>
  </Accordion>

  <Accordion title="Message data">
    <ResponseField name="message_type" type="text">
      Type of the incoming message: `text`, `audio`, `image`, or `document`
    </ResponseField>

    <ResponseField name="incoming_message" type="boolean">
      `true` for this trigger — confirms this is an inbound message from the contact
    </ResponseField>

    <ResponseField name="send_by" type="text">
      Empty on this incoming-only trigger. On the incoming **and outgoing** trigger, this identifies the sending system or teammate (see below)
    </ResponseField>

    <ResponseField name="was_message_by_human" type="boolean">
      `true` when a person sent the message
    </ResponseField>

    <ResponseField name="attachment_url" type="text">
      Public URL of any file the contact attached (image, document, audio). Empty if no attachment
    </ResponseField>

    <ResponseField name="is_scheduled" type="boolean">
      `true` if triggered by a scheduled message being delivered; `false` for real-time messages
    </ResponseField>

    <ResponseField name="referral" type="object">
      Present when the inbound message came from a Click-to-WhatsApp ad or post. Includes `source_type`, `source_id`, `source_url` (platform), `headline`, `body`, `media_type`, creative URLs, and `ctwa_clid`. Omitted on ordinary chats and on most follow-up messages. See [Click-to-WhatsApp ads](/guides/notifyer-system/api/incoming-message#click-to-whatsapp-ads).
    </ResponseField>
  </Accordion>

  <Accordion title="Conversation history">
    <ResponseField name="last_messages" type="text">
      JSON array of recent messages. Each item includes: `type` (user/bot), `content`, `timestamp`, `content_type`. Useful for passing full history to an AI
    </ResponseField>

    <ResponseField name="last_message_of_user" type="text">
      The most recent message sent by the contact — the message that triggered this run
    </ResponseField>

    <ResponseField name="last_message_of_bot" type="text">
      The most recent message your business sent to this contact — helps AI avoid repeating itself
    </ResponseField>

    <ResponseField name="user_last_message_time" type="number">
      Unix timestamp (ms) of when the contact's last message was received
    </ResponseField>

    <ResponseField name="bot_last_message_time" type="number">
      Unix timestamp (ms) of when your business last messaged this contact
    </ResponseField>

    <ResponseField name="conversation_paragraph" type="text">
      A flat, readable version of the full conversation history — ideal for passing directly to an AI/LLM prompt without parsing the `last_messages` JSON array
    </ResponseField>
  </Accordion>

  <Accordion title="AI context & automation fields">
    <ResponseField name="note" type="text">
      The AI context note stored on this contact in Notifyer. Contains lead details: name, email, preferences, background, language, etc. Set this via the **Update a Contact** action or directly in the Notifyer console
    </ResponseField>

    <ResponseField name="note_automation" type="text">
      Automation instructions for the AI — rules the AI follows automatically based on conversation events (e.g. "If budget confirmed and timeline under 6 months, notify the agent within 1 hour")
    </ResponseField>

    <ResponseField name="scheduled_messages" type="text">
      Description of any messages currently queued/scheduled to be sent to this contact at a future time
    </ResponseField>
  </Accordion>
</AccordionGroup>

***

#### Incoming & Outgoing Messages from console (Notifyer System)

<Info>
  **Type:** Instant Trigger | **Connection:** Notifyer only
</Info>

Fires on **both incoming and outgoing** messages — every message sent or received in your Notifyer console triggers this, including messages **typed by hand in the WhatsApp Business app**. Use it for conversation logging, CRM sync, or automations that must react when a teammate replies on their phone.

**Description in Make:** *"Get your sent and incoming messages data through a single webhook."*

**How to set up:** Follow the same [5-step trigger setup guide](#setting-up-a-notifyer-trigger-in-make) above. In Step 1, select **Incoming & Outgoing Messages from console (Notifyer System)** instead.

**Key difference:** This trigger also fires when your business sends a message. Use the `incoming_message` field to branch your logic:

* `incoming_message = true` → a contact sent your business a message
* `incoming_message = false` → your business sent a message to a contact (phone app, Notifyer inbox, or automation)

**Output fields:** Identical to the **Incoming Messages from console** trigger above, with these differences:

<ResponseField name="incoming_message" type="boolean">
  `true` when the contact sent a message, `false` when your business sent a message. Add a **Router** or **Filter** module after this trigger to branch logic based on direction
</ResponseField>

<ResponseField name="send_by" type="text">
  Which system or person sent an outgoing message: `"WhatsApp App"` for the WhatsApp Business app, the teammate's name for the Notifyer chat inbox, or the automation/app name for Make, Zapier, n8n, or API
</ResponseField>

<ResponseField name="was_message_by_human" type="boolean">
  `true` when a person sent the message (phone app or Notifyer inbox). `false` when a bot or automation sent it
</ResponseField>

<Note>
  The `scheduled_messages` field is only available in the **Incoming Messages from console** trigger, not this one.
</Note>

## Incoming and outgoing WhatsApp messages

Notifyer delivers **both incoming and outgoing** messages to your webhook or automation trigger — including messages typed by hand in the **WhatsApp Business app** on your phone.

This is possible because Notifyer supports [Meta WhatsApp Coexistence](/guides/notifyer-system/embedding-process#whatsapp-coexistence). You keep using WhatsApp Business on your phone; those hand-typed replies still reach an external webhook and can start an automation. They are not limited to the Notifyer web inbox.

<Frame>
  <iframe title="Trigger n8n workflows with WhatsApp messages" />
</Frame>

The payload is the same whether you use [n8n](/guides/notifyer-system/n8n-overview), [Make](/guides/notifyer-system/make-overview), [Zapier](/guides/notifyer-system/zapier-overview), or a [custom webhook](/guides/notifyer-system/api/incoming-message). [Watch the walkthrough on YouTube](https://www.youtube.com/watch?v=UfW-KwS4gBI).

### Direction, sending system, and team member

Use these three fields to tell *what happened* and *who sent it*:

<ResponseField name="incoming_message" type="boolean">
  `true` when a contact sent a message **to** your business. `false` when your business sent a message **to** the contact (outgoing). Filter on this field to run logic only for one direction.
</ResponseField>

<ResponseField name="send_by" type="string">
  Which system or person sent an **outgoing** message:

  | `send_by` value | Meaning |
  | - | - |
  | `WhatsApp App` | Typed by hand in the WhatsApp Business app on a phone |
  | A team member's name (for example `Axel Meta`) | Sent from the Notifyer chat inbox by that logged-in user |
  | An automation or app name (Make, Zapier, n8n, API, bot) | Sent by that integration or bot |

  Empty or omitted on incoming messages.
</ResponseField>

<ResponseField name="was_message_by_human" type="boolean">
  `true` when a person sent the message (WhatsApp Business app or Notifyer chat inbox). `false` when a bot or automation sent it. Combine with `send_by` to see both *whether* a human sent it and *which teammate or system* did.
</ResponseField>

### Example payload: message typed on the phone

This is the JSON Notifyer POSTs when someone types a reply in the WhatsApp Business app. `incoming_message` is `false`, `send_by` is `"WhatsApp App"`, and `was_message_by_human` is `true`.

```json theme={null}
{
  "last_messages": "[{\"type\":\"bot\",\"content\":\"Hello n8n\",\"timestamp\":\"2026-08-15T12:24:47.000Z\",\"content_type\":\"text\"},{\"type\":\"user\",\"content\":\"hi\",\"timestamp\":\"2026-08-12T12:27:42.746Z\",\"content_type\":\"text\"}]",
  "conversation_paragraph": "Bot (12:24:47 PM): Hello n8n ; User (12:27:42 PM): hi",
  "phone_number": 14155552671,
  "recipient_name": "Alex Martinez",
  "user_id": "158c59e1-ea85-4d0b-b70c-65328ba67a8e",
  "last_message_of_user": "hi",
  "last_message_of_bot": "Hello n8n",
  "message_type": "text",
  "user_last_message_time": 1786722580,
  "bot_last_message_time": 1786797014,
  "attachment_url": null,
  "note": "email: alex\nName: Alex",
  "note_automation": "email: alex\nName: Alex",
  "labels": "n8n, webhook-test",
  "incoming_message": false,
  "send_by": "WhatsApp App",
  "was_message_by_human": true
}
```

<Note>
  `last_message_of_bot` is the last message **your business** sent — whether a human typed it in the WhatsApp Business app or the Notifyer inbox, or a bot/automation sent it. `last_messages` is a JSON **string** of the last \~20 messages (parse it before iterating). `phone_number` may arrive as a number rather than a string.
</Note>

When the same person sends from the Notifyer chat inbox instead of the phone app, the payload is identical except:

```json theme={null}
{
  "incoming_message": false,
  "send_by": "Axel Meta",
  "was_message_by_human": true
}
```

### Click-to-WhatsApp ad attribution

When a contact messages you after tapping a **Click-to-WhatsApp** ad (Facebook, Instagram, or WhatsApp Status), Meta includes a `referral` object on that inbound event. Notifyer forwards it in [webhook](/guides/notifyer-system/api/incoming-message#click-to-whatsapp-ads) and trigger data (n8n, Make, Zapier).

Use it to see **which ad, creative, and platform** produced the lead — then label the chat, route it, or send `ctwa_clid` back to Meta for campaign optimization.

<Note>
  `referral` is typically present on the **first inbound message** after the ad click. Later messages in the same conversation usually omit it. Persist `ctwa_clid` and `source_id` as soon as you see them.
</Note>

| Field | What it tells you |
| - | - |
| `source_type` | `"ad"` for an ad, `"post"` for an organic post |
| `source_id` | Ad or post ID — use this to group leads by creative |
| `source_url` | Where they tapped (Instagram permalink, Facebook/ad URL) |
| `headline` / `body` | Ad copy the lead saw |
| `media_type` | `"image"` or `"video"` |
| `image_url` / `video_url` | Creative asset URL |
| `ctwa_clid` | Click ID for Meta Conversions API attribution |

```json theme={null}
{
  "incoming_message": true,
  "last_message_of_user": "Quiero información",
  "referral": {
    "source_type": "ad",
    "source_id": "52540693396957",
    "source_url": "https://www.instagram.com/p/DZiVBz7gAF9/",
    "headline": "Expo Nissan",
    "body": "Aprovechá la EXPONISSAN y llevate tu nuevo Nissan Kicks Play Sense MT.",
    "media_type": "image",
    "image_url": "https://scontent.xx.fbcdn.net/v/t45.1600-4/example.jpg",
    "ctwa_clid": "AfhN-JKvx8HeFTmfB-Tu11zktQRJ-MNdMV1mwvDNxHnpYrGl-jVf3OEFhLva_MP41zYRe5ErUteWFn3v4gkkjzfIEVr9J_u8GAo3-o6DqShykM4Zsl14FcU5MyThsCoQ"
  }
}
```

If your delivery includes the Cloud API envelope instead of a flattened Notifyer payload, the same object lives at `entry[].changes[].value.messages[].referral`. Full field reference and a complete example: [Message webhooks — Click-to-WhatsApp ads](/guides/notifyer-system/api/incoming-message#click-to-whatsapp-ads).

***

### Actions

Actions perform operations in Notifyer System — sending messages, scheduling follow-ups, and updating contacts.

***

#### Send WhatsApp Message

<Info>
  **Type:** Action | **Connection:** Notifyer only
</Info>

**Description in Make:** *"Send WhatsApp Messages using the official WhatsApp API. You can add labels to a WhatsApp conversation and also write notes about the lead that will appear in Whatsable's chat interface."*

Send a WhatsApp message immediately to any phone number. Supports both **template messages** (to start a new conversation) and **non-template messages** (within an active 24-hour window). Labels and notes set here appear directly in your Notifyer console — making this the primary send module for Notifyer System users.

**API endpoint:** `https://api.insightssystem.com/api:pqxobaAo/send`

**How to configure:**

<Steps>
  <Step title="Add the module">
    Click **+** → search for **Whatsable** or **Whatsable for WhatsApp Business** → under **Actions**, select **Send WhatsApp Message**
  </Step>

  <Step title="Select your connection">
    Choose your existing connection or create a new one with your **Notifyer API key**
  </Step>

  <Step title="Choose your configuration">
    Select from the **Configuration** dropdown:

    <Tabs>
      <Tab title="Send WhatsApp Template (to start conversation)">
        Use this to **initiate a new conversation** or reach out proactively. Requires a Meta-approved template.

        <ResponseField name="Phone Number" type="text">
          Recipient's phone number in international format — digits only, no `+` or spaces (e.g. `14155550187`)
        </ResponseField>

        <ResponseField name="Template Name or ID" type="dropdown">
          Select from your approved templates. The dropdown shows a live preview of each template's body, language, and category
        </ResponseField>

        <ResponseField name="Body 1, Body 2, ... (variables)" type="text">
          If your template has variables (`{{1}}`, `{{2}}`...), a field appears for each. Map them to dynamic data from previous modules
        </ResponseField>

        <ResponseField name="Media" type="text">
          If your template has a media header (image, video, document), enter the publicly accessible URL of that file
        </ResponseField>

        <ResponseField name="Visit Website URL" type="text">
          If your template has a dynamic URL button, enter the URL value including the dynamic portion
        </ResponseField>

        <ResponseField name="Note" type="text">
          AI context about this contact (name, email, preferences, language). The AI reads this to personalize future replies and qualify leads more accurately
        </ResponseField>

        <ResponseField name="Label Names or IDs" type="multiselect">
          Labels to apply to this conversation for internal tracking and routing. Labels appear in your Notifyer console
        </ResponseField>
      </Tab>

      <Tab title="Send a non-template message (person must write to you first)">
        Use this to send a message **within an active conversation** — only possible within 24 hours of the contact's last incoming message.

        <ResponseField name="Recipient Phone Number" type="text">
          Phone number in international format — digits only (e.g. `14155550187`)
        </ResponseField>

        <ResponseField name="Message Type" type="dropdown">
          Choose the type of message to send:

          <AccordionGroup>
            <Accordion title="Text Message">
              <ResponseField name="Message Content" type="text">
                The text content to send
              </ResponseField>

              <ResponseField name="Enable Link Preview" type="boolean">
                Set to `true` to show a URL preview card when the message contains a link. Default: `false`
              </ResponseField>
            </Accordion>

            <Accordion title="Image Message">
              <ResponseField name="Image URL" type="url">
                Publicly accessible URL of the image (JPEG, PNG, etc.)
              </ResponseField>

              <ResponseField name="Caption" type="text">
                Optional caption text below the image
              </ResponseField>
            </Accordion>

            <Accordion title="Video Message">
              <ResponseField name="Video URL" type="url">
                Publicly accessible URL of the video (MP4, etc.)
              </ResponseField>

              <ResponseField name="Caption" type="text">
                Optional caption text below the video
              </ResponseField>
            </Accordion>

            <Accordion title="Document Message">
              <ResponseField name="Document URL" type="url">
                Publicly accessible URL of the document (PDF, DOCX, etc.)
              </ResponseField>

              <ResponseField name="Caption" type="text">
                Optional caption for the document
              </ResponseField>

              <ResponseField name="Filename" type="text">
                Filename to display (e.g. `invoice-2026.pdf`)
              </ResponseField>
            </Accordion>

            <Accordion title="Audio Message">
              <ResponseField name="Audio URL" type="url">
                Publicly accessible URL of the audio file (MP3, OGG, etc.)
              </ResponseField>
            </Accordion>
          </AccordionGroup>
        </ResponseField>

        <ResponseField name="Label Names or IDs" type="multiselect">
          Labels to apply to this conversation. Labels appear in your Notifyer console
        </ResponseField>

        <ResponseField name="Note" type="text">
          AI context note for this contact — set or update the note that the AI reads to personalize replies
        </ResponseField>
      </Tab>
    </Tabs>
  </Step>
</Steps>

***

#### Schedule a follow-up Message

<Info>
  **Type:** Action | **Connection:** Notifyer only
</Info>

**Description in Make:** *"Schedule a follow-up to get sent later and add conditions so it only gets sent if the lead did not reply to you."*

Schedule a WhatsApp message to be sent at a **future time**, with an optional **reply condition** that automatically cancels the message if the recipient responds before it sends. This is one of Notifyer's most powerful automation features — use it to build no-reply follow-up sequences, re-engagement drips, and smart nurture workflows.

**How to configure:**

<Steps>
  <Step title="Add the module">
    Click **+** → search for **Whatsable** or **Whatsable for WhatsApp Business** → under **Actions**, select **Schedule a follow-up Message**
  </Step>

  <Step title="Select your connection">
    Choose your **Notifyer only** connection
  </Step>

  <Step title="Choose your message type">
    Select from the **Configuration** dropdown — either a template message or a non-template message. The fields are identical to the **Send WhatsApp Message** action above (phone number, template/message type, variables, labels, note).
  </Step>

  <Step title="Set when to send it">
    <Tabs>
      <Tab title="Relative (Delay)">
        Send the message after a delay from the time the scenario runs:

        <ResponseField name="Delay Value" type="select">
          Choose: 1, 2, 3, 4, 5, 10, 15, 20, 30, 60, 90, or 120
        </ResponseField>

        <ResponseField name="Delay Unit" type="select">
          Choose: **Minutes**, **Hours**, or **Days**
        </ResponseField>
      </Tab>

      <Tab title="Specific Date & Time">
        Send the message at an exact date and time:

        <ResponseField name="Date & Time" type="datetime">
          The exact date and time to send the message
        </ResponseField>

        <ResponseField name="Timezone" type="select">
          The timezone for the scheduled time — full global timezone list available (GMT-11 through GMT+12)
        </ResponseField>
      </Tab>
    </Tabs>
  </Step>

  <Step title="Set a reply condition (recommended)">
    The reply condition tells Notifyer to **cancel the scheduled message** if the recipient replies within the specified timeframe — preventing follow-ups to contacts who are already engaged.

    <ResponseField name="Reply Condition" type="select">
      | Condition | When the message is cancelled |
      | - | - |
      | Recipient did not reply after my last message | Cancelled if the contact replies at any point before scheduled send |
      | Recipient never replied to any of my messages | Cancelled only if the contact has never replied to you at all |
      | Recipient did not reply within 20 minutes | Cancelled if contact replies within 20 minutes |
      | Recipient did not reply within 45 minutes | Cancelled if contact replies within 45 minutes |
      | Recipient did not reply within 3 hours | Cancelled if contact replies within 3 hours |
      | Recipient did not reply within 6 hours | Cancelled if contact replies within 6 hours |
      | Recipient did not reply within 12 hours | Cancelled if contact replies within 12 hours |
      | Recipient did not reply within 24 hours | Cancelled if contact replies within 24 hours |
      | Recipient did not reply within 48 hours | Cancelled if contact replies within 48 hours |
      | Recipient did not reply within 72 hours | Cancelled if contact replies within 72 hours |
    </ResponseField>

    <Tip>
      **"Recipient did not reply after my last message"** is the recommended default for most follow-up sequences — it ensures no follow-up is sent to contacts who are already in conversation with you.
    </Tip>
  </Step>

  <Step title="Set a label condition (optional)">
    Restrict the scheduled message to only send if the contact has (or does not have) a specific label:

    <ResponseField name="Label Condition" type="select">
      **Include** — only send if the contact has this label\
      **Does Not Include** — only send if the contact does NOT have this label
    </ResponseField>

    <ResponseField name="Label" type="select">
      The label to evaluate against
    </ResponseField>
  </Step>
</Steps>

<Note>
  Scheduled messages are visible in your Notifyer console under the contact's conversation. You can view or cancel them there at any time.
</Note>

***

#### Update a Contact

<Info>
  **Type:** Action | **Connection:** Notifyer only
</Info>

**Description in Make:** *"Assign conversation to someone in your team, Add information in the notes, add/remove labels. Simply put the phone number and what information you want to change. This appears in the chat interface of our system."*

Update a contact's details in your Notifyer console — set their display name, add or remove labels, or update the AI context note on their conversation. Use this to keep Notifyer contacts in sync with your CRM, form responses, or other external data.

**API endpoint:** `https://api.insightssystem.com/api:hFrjh8a1/make/recipient/details/update` (PUT)

**How to configure:**

<Steps>
  <Step title="Add the module">
    Click **+** → search for **Whatsable** or **Whatsable for WhatsApp Business** → under **Actions**, select **Update a Contact**
  </Step>

  <Step title="Select your connection">
    Choose your **Notifyer only** connection
  </Step>

  <Step title="Fill in the fields">
    <ResponseField name="Phone Number" type="text">
      The phone number of the contact to update, in international format — digits only (e.g. `14155550187`). This is used to look up the contact in Notifyer
    </ResponseField>

    <ResponseField name="Display Name" type="text">
      Update the display name shown for this contact in the Notifyer chat interface
    </ResponseField>

    <ResponseField name="Add a Note" type="text">
      Set or update the AI context note for this contact. The AI reads this field to personalize conversations. A well-structured note significantly improves AI response quality.

      **Recommended note format:**

      ```
      email: john@example.com | Name: John Smith
      Looking for: 3BR house, $500k budget, north suburbs
      Pre-approved: Yes | Language: English
      Best time to contact: evenings after 6pm
      ```
    </ResponseField>

    <ResponseField name="Add Label Names or IDs" type="multiselect">
      One or more labels to **add** to this contact. Labels appear in the Notifyer console and can be used for routing, filtering, and automation conditions
    </ResponseField>

    <ResponseField name="Remove Label Names or IDs" type="multiselect">
      One or more labels to **remove** from this contact. Select **Remove All** to clear all labels from this contact at once
    </ResponseField>
  </Step>
</Steps>

<Tip>
  Place **Update a Contact** at the very start of your scenario — before sending any message — to populate the AI Note from form or CRM data. This ensures the AI has full context before the first message is even sent.
</Tip>

***

### Search

***

#### Get delivery status of a message

<Info>
  **Type:** Search | **Connection:** Notifyer only
</Info>

**Description in Make:** *"Check if the message was delivered or not. Use this if you're not sure the number is correct and want to check if it was delivered and want to send a fallback email."*

Check whether a previously sent WhatsApp message was delivered. Use this to build fallback automation — if a message was not delivered (e.g. incorrect number), automatically trigger an alternative action such as sending a fallback email.

**API endpoint:** `https://api.insightssystem.com/api:5l-RgW1B/conversation/{{messageId}}` (GET)

**How to configure:**

<Steps>
  <Step title="Add the module">
    Click **+** → search for **Whatsable** or **Whatsable for WhatsApp Business** → under **Searches**, select **Get delivery status of a message**
  </Step>

  <Step title="Select your connection">
    Choose your **Notifyer only** connection
  </Step>

  <Step title="Enter the Message ID">
    <ResponseField name="Message ID" type="text">
      The ID of the message to check. This is the ID returned in the output bundle of a previous **Send WhatsApp Message** or **Schedule a follow-up Message** action in the same scenario
    </ResponseField>
  </Step>
</Steps>

<Tip>
  Connect a **Router** module after this search to handle two paths: one for successfully delivered messages, and one for undelivered messages where you trigger a fallback (e.g. send a Gmail or Outlook email).
</Tip>

***

## Building a complete scenario: step-by-step example

Here is a practical end-to-end example: **New lead from a form → AI context set → Template message sent → Conditional follow-up scheduled**

<Steps>
  <Step title="Trigger: New form submission">
    Start with a **Google Forms**, **Typeform**, or **Jotform** instant trigger that fires when someone fills in your lead capture form
  </Step>

  <Step title="Action: Update a Contact">
    Add **Notifyer — Update a Contact**. Map form fields into the Note field:

    ```
    email: {{email}} | Name: {{name}} | Budget: {{budget}} | Language: {{language}}
    ```

    Add relevant labels: `New Lead`, `Form Submission`

    This gives the AI complete context before any conversation starts
  </Step>

  <Step title="Action: Send WhatsApp Message (Template)">
    Add **Notifyer — Send WhatsApp Message** set to the template configuration. Select your approved welcome template and map the recipient's phone number and any template variables from the form data
  </Step>

  <Step title="Action: Schedule a follow-up Message">
    Add **Notifyer — Schedule a follow-up Message**. Configure:

    * Message: a follow-up template (e.g. `Hi {{1}}, just checking in...`)
    * Schedule: 24 hours (Relative)
    * Reply condition: **Recipient did not reply after my last message**

    This follow-up cancels automatically if the lead responds to your first message
  </Step>

  <Step title="Test and activate">
    1. Click **Run once** to test with real data
    2. Verify each module shows a green checkmark
    3. Toggle the scenario **Active** switch to go live
  </Step>
</Steps>

***

## Example use cases

<CardGroup>
  <Card title="AI chatbot lead qualification" icon="robot">
    Trigger on incoming messages, pass the `conversation_paragraph` and `note` to OpenAI, then send the AI's reply back via Send WhatsApp Message
  </Card>

  <Card title="Smart follow-up sequences" icon="calendar-clock">
    Schedule a series of follow-ups with reply conditions — they automatically cancel when the lead engages
  </Card>

  <Card title="CRM-to-WhatsApp sync" icon="database">
    When a deal stage changes in HubSpot or Pipedrive, use Update a Contact to update the AI note, then send a relevant WhatsApp template
  </Card>

  <Card title="Form-to-WhatsApp onboarding" icon="file-lines">
    When a form is submitted, instantly set AI context via Update a Contact, then send a personalized onboarding template message
  </Card>

  <Card title="Delivery fallback" icon="envelope">
    Use Get delivery status after sending a message — if undelivered, route to a fallback email via Gmail or Outlook
  </Card>

  <Card title="Full conversation logging" icon="list">
    Use Incoming & Outgoing Messages trigger to log every WhatsApp exchange to a Google Sheet, Airtable, or CRM
  </Card>
</CardGroup>

***

## Best practices

<AccordionGroup>
  <Accordion title="Set the AI Note before sending" icon="robot">
    Always use **Update a Contact** before **Send WhatsApp Message** in new-lead scenarios. Setting the `note` field with structured lead data (name, email, preferences, language, budget) dramatically improves AI conversation quality and lead qualification accuracy.
  </Accordion>

  <Accordion title="Always use reply conditions on follow-ups" icon="shield-check">
    Set a reply condition on every **Schedule a follow-up Message**. "Recipient did not reply after my last message" is the safest choice — it ensures no follow-up annoys contacts who are already in an active conversation with you. This also protects your WhatsApp account reputation.
  </Accordion>

  <Accordion title="Use labels and notes on every send" icon="paper-plane">
    The **Send WhatsApp Message** action lets you attach labels and a note alongside every message. Use labels to tag conversations (e.g. `Hot Lead`, `Form Submission`) and the note field to keep AI context current. Both appear immediately in your Notifyer console.
  </Accordion>

  <Accordion title="Use conversation_paragraph for AI prompts" icon="paragraph">
    When building AI chatbot scenarios, pass the `conversation_paragraph` field to your AI model. It is a pre-formatted, flat text version of the conversation — much simpler to include in a prompt than parsing the `last_messages` JSON array.
  </Accordion>

  <Accordion title="Use Incoming & Outgoing trigger for full logging" icon="list">
    If you need to log every message exchange to a CRM or database, use **Incoming & Outgoing Messages from console** and filter by `incoming_message` to handle both directions with separate scenario branches.
  </Accordion>

  <Accordion title="Capture Click-to-WhatsApp referral on the first message" icon="bullhorn">
    When `referral` is present, store `source_id`, `source_url`, `headline`, and `ctwa_clid` on the contact immediately. Later messages in the same chat usually omit `referral`. Use `source_url` to see Instagram vs Facebook, and `source_id` to compare creatives.
  </Accordion>

  <Accordion title="Phone number format" icon="phone">
    Always provide phone numbers in full international format — digits only, no `+`, spaces, or dashes (e.g. `14155550187` for US, `447911123456` for UK, `966501234567` for Saudi Arabia).
  </Accordion>
</AccordionGroup>

***

## Troubleshooting

<AccordionGroup>
  <Accordion title="Trigger not firing?" icon="circle-exclamation">
    <Steps>
      <Step title="Check the scenario is active">
        Instant triggers only fire when the scenario is toggled **Active** in Make. Also confirm the schedule is set to **Immediately as data arrives**
      </Step>

      <Step title="Verify the webhook is configured">
        Open the trigger module and confirm a webhook is selected in the **Webhook** dropdown and a **Webhook URL** is displayed. If the field is empty, follow the [trigger setup guide](#setting-up-a-notifyer-trigger-in-make) to create one
      </Step>

      <Step title="Verify your connection">
        Open the connection settings and confirm your Notifyer API key is valid and the connection shows a green tick
      </Step>

      <Step title="Re-register the webhook">
        Try deactivating and reactivating the scenario — this re-registers the webhook with Notifyer. Check your Notifyer console to confirm messages are arriving there
      </Step>

      <Step title="Check Notifyer console">
        If messages appear in your Notifyer console but the trigger does not fire, contact support
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Messages not sending?" icon="message-xmark">
    <Steps>
      <Step title="Check the connection">
        Verify your Notifyer API key is valid and the correct connection is selected
      </Step>

      <Step title="Check phone number format">
        Phone number must be digits only, full international format, no `+` or spaces (e.g. `14155550187`)
      </Step>

      <Step title="Template not approved?">
        Ensure the selected template has **Approved** status in your Notifyer dashboard. Pending or rejected templates will cause an error
      </Step>

      <Step title="24-hour window for non-template">
        Non-template messages can only be sent within 24 hours of the contact's last incoming message. Outside this window you must use a template
      </Step>

      <Step title="Check subscription credits">
        Verify your Notifyer subscription is active and has sufficient message credits
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Template variables not populating?" icon="brackets-curly">
    <Steps>
      <Step title="Fill all required variable fields">
        All body variable fields (Body 1, Body 2, etc.) are required — ensure none are empty or mapped to empty values
      </Step>

      <Step title="Check the template preview">
        The template dropdown shows a live preview of the body text and example variable values — use this as a reference to understand what each variable slot expects
      </Step>

      <Step title="Media URL must be public">
        If your template has a media header, the URL must be publicly accessible. Test it in an incognito browser window
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Scheduled message was not sent?" icon="clock">
    <Steps>
      <Step title="Reply condition may have cancelled it">
        If you set a reply condition and the contact replied before the scheduled time, the message was intentionally cancelled. Check the contact's conversation in your Notifyer console
      </Step>

      <Step title="Check the scheduled time">
        Verify the delay value and unit are correct (minutes vs hours vs days)
      </Step>

      <Step title="Check scenario run history">
        Go to Make scenario history to confirm the Schedule a follow-up module executed without errors at the time the trigger fired
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Update a Contact changes not appearing in Notifyer?" icon="user-pen">
    <Steps>
      <Step title="Verify the phone number">
        The phone number must exactly match the contact's number in Notifyer. If the contact doesn't exist yet, the update creates the record
      </Step>

      <Step title="Check you're using the right connection">
        Update a Contact requires the **Notifyer only** connection — make sure you are not using a different connection type
      </Step>
    </Steps>
  </Accordion>
</AccordionGroup>

***

## Need help?

<CardGroup>
  <Card title="Email support" icon="envelope" href="mailto:team@whatsable.app">
    Contact [team@whatsable.app](mailto:team@whatsable.app)
  </Card>

  <Card title="Schedule a demo" icon="calendar" href="https://tidycal.com/axelmeta/notifyer-systems-demo">
    Book a personalized walkthrough
  </Card>

  <Card title="Live chat" icon="message-dots">
    Click the green chat button in the bottom right corner of the Notifyer System dashboard
  </Card>
</CardGroup>


# How do I create and approve WhatsApp templates in Whatsable?
Source: https://docs.whatsable.app/guides/notifyer-system/message-templates

Create and approve WhatsApp message templates in the Whatsable console: super-admin submit, variables, languages, Meta review, and recreate instead of edit.

Yes. A **super-admin** creates a WhatsApp message template in the Whatsable console, submits it to Meta, and can send it only after Meta marks it **approved**. Use this page for the operator path: who is allowed to create, which fields you fill, how status moves from pending to approved or rejected, and what to do when the text must change or you connect a new number.

Creating a template is **not** broadcasting, and it is **not** the send-template API. Those flows only use a template that already exists and is approved. Outside the 24-hour customer-service window, WhatsApp only allows approved templates for business-initiated messages.

## Prerequisites

* **Whatsable account** on **Bulk Message**, **Pro**, or **Agency**. Template management is on all three. Sign in at [dashboard.whatsable.app/signin](https://dashboard.whatsable.app/signin).
* **Super-admin role** on that account. Only super-admins can create templates. A normal admin does not have that access. If create is missing, this is the usual cause. The rest of the role matrix is not documented here.
* **WhatsApp Business number connected** through Whatsable (Embedded Signup / Coexistence — keep the WhatsApp Business app; do not uninstall it after connect). Submit uses that number’s WhatsApp credentials.
* **Meta Business Portfolio** (business.facebook.com), not a personal Facebook profile. Embedded Signup may ask for a website; an Instagram profile link or Facebook page link is enough if you have no site.
* **Meta payment method** before you **send** template messages. Meta charges per template message. A missing card is a send failure, not proof the template was rejected.
* You do **not** need Make, Zapier, n8n, or the API to create a template in the console.

<Info>
  How-to video (EN): [How to create a WhatsApp message template](https://youtu.be/QvnNp47txe8). Templates and broadcasts are different topics — do not swap the videos. ES / PT / FR versions exist on the same topic.
</Info>

***

## Operator path — create and submit

Open **Settings → Templates** and follow the steps below. Button and sidebar labels can vary by workspace. This page documents the create and submit path that is available today — not every optional console control.

### 1. Open templates

In the Whatsable console, open **Settings → Templates**. That is where you check status. Only **Meta-approved** templates appear in send dropdowns (broadcasts, chat, monday.com Send Template, and similar).

### 2. Start a new template (super-admin)

A normal admin cannot create. There is no documented “edit and resubmit.” If you need different text, you create another template (you can delete the old one).

### 3. Fill the fields and submit to Meta

Whatsable sends the template to Meta for review. It is stored for the workspace only if Meta accepts the submission. A duplicate **name** already on the workspace is rejected (you cannot create a second template with the same name).

### 4. Read status

After submit, status is **pending** until Meta finishes review. Open **Settings → Templates** again to refresh pending items against Meta (the console list updates pending templates when it loads). You do not approve the template yourself.

* **Approved** — ready for broadcasts, inbox/API sends, and integration dropdowns.
* **Rejected** — Meta declined it. Create a new template. You cannot edit the rejected one and resubmit it. If the console does not show a rejection reason, check Meta Business Manager.

### 5. Use it only when approved

Pending templates do not send reliably. A test or template send that returns WhatsApp error (100), “Unsupported post request… object with ID 'messages'…”, is often **this template still pending**, not a disconnected number. If status is already approved and the error remains, then check that the number is still connected.

Copying an old template’s text: open **preview** on the old template, then paste into the new one. That is the supported shortcut when you change numbers or recreate. There is no transfer of approved templates onto a different WhatsApp number.

***

## Field inventory

The names below match the create payload and the rules the console enforces. On-screen labels may differ slightly from these payload names.

### Template name

One name per template, unique in the workspace.

* Lowercase letters, digits, and underscores. The console forces lowercase.
* Must start with a letter, not a digit.
* No spaces (use underscores).
* Maximum **512** characters.
* Examples that pass: `order_confirmation`, `invoice_en`. Examples that fail: `OrderConfirmation`, `2fa_code`, `promo banner`.

This is the template **name**, not a separate display name. A typed display-name field is not documented on this page.

### Category

One of:

| Category | Typical use |
| - | - |
| **Marketing** | Promotions, offers, announcements |
| **Utility** | Order updates, confirmations, service notices |
| **Authentication** | One-time verification codes |

Meta prices template conversations by category. Whatsable does not add a markup on Meta fees. Pick the category that matches the content. A mismatch is a common rejection reason; this page does not invent Meta’s policy text.

**Authentication** does not use a free-form body you write. The create payload builds a verification-code message, with an optional security line (“do not share this code”) and a code expiry in minutes (payload default **10**). An OTP button label exists on that payload (default copy is “Copy Code”). Use the authentication options shown in your console. Importing an authentication template that was created in Meta’s own manager is not covered on this page.

### Language

Each template has **one** language code (examples: `en`, `es`, `fr`). Another language is **another template** (its own name, its own Meta review). There is no documented switch that adds a language onto an existing approved template.

### Body and variables

For Marketing and Utility, you write the body. Personalization uses numbered placeholders, in order, starting at `{{1}}`:

`Hello {{1}}, your order #{{2}} is confirmed.`

Every placeholder needs an **example value** for Meta’s review (realistic dummy data, not empty). Those examples are for the reviewer. Real values are supplied later, per recipient, when you send or broadcast (`body1`, `body2`, … on the send API and on broadcast CSVs).

Do not document named placeholders such as `{{company}}` or `{{name}}` for this console. That syntax appears on an older mid-layer templates article and is not the Whatsable create payload.

Header **text** variables and a free-text footer on Marketing/Utility templates are not documented as console fields on this page. The authentication security line above is the footer this create payload actually sets.

### Header media type

| Type | Header | What you supply |
| - | - | - |
| Text | None | Body only |
| Image | Image | PNG or JPG, uploaded from a URL before submit |
| Video | Video | MP4, uploaded before submit |
| Document | Document | PDF, uploaded before submit |

The console uploads the file and stores a media handle on the template. At **send** time, a public media URL can still be passed per message when the template expects media — that is the [template message API](/guides/notifyer-system/api/template-message) and the broadcast CSV `media` column, not a second create step. Broader file types and size caps on that send page are send rules, not extra create formats.

### Buttons (optional)

The create payload accepts these kinds. Limits are from the console create path:

| Kind | Payload shape | Max |
| - | - | - |
| Quick reply | Button label text | 10 |
| Visit website | Button text, static URL, or a base URL plus a dynamic suffix | 2 |
| Call phone number | Button text and phone number | 1 |
| Copy offer code | The code to copy | 1 |

Total buttons on one template: **10**. A dynamic website URL is a fixed base plus a per-recipient suffix (broadcast column `button_dynamic_url_value`, or the send API’s dynamic website flag).

### Status values you will see

Pending, approved, or rejected. Casing in API payloads varies (`PENDING` vs `approved`); do not treat letter case as a customer-facing label. Only approved templates are offered when sending.

***

## Limits and what this is not

<Warning>
  **Only super-admins create templates.** A normal admin cannot. **You cannot edit** a submitted template. Recreate, resubmit, and delete the old one if you no longer need it. Approved templates **do not move** to a new WhatsApp number.
</Warning>

* **Meta review time is not a guarantee.** Meta usually approves within a few minutes and can take up to about 24 hours. Do not promise a minute, and do not promise 24–48 hours. If it is still pending, wait and recheck **Settings → Templates** rather than creating duplicates (duplicate names are blocked anyway).
* **No in-console edit.** Rejected or outdated copy means a new template. Use **preview** on the old one to copy the text.
* **New number:** recreate and resubmit every template. Old approvals do not apply.
* **Sends need an approved template** when you are outside the 24-hour window, or when you are opening the conversation. Inside 24 hours of the contact’s last message, free-form (non-template) messages are allowed. Business-initiated template conversations also follow Meta’s portfolio tiers (unverified about 250/day, then higher tiers after verification). Those caps are Meta’s, not a Whatsable messages-per-minute number. This page does not invent a Whatsable RPM.
* **No native drip builder** and **no typing-indicator dots.** Sequences of templates over days run in Make, Zapier, or n8n.
* **Template management is not a plan upsell.** Bulk Message, Pro, and Agency all include it. Broadcasting those templates is a different page. Scheduled broadcasts are available on Bulk Message, Pro, and Agency.
* **ProactiveBot** (Pro and Agency) can generate a follow-up template when none fits. That does not replace this create flow, and it is not documented as a way around the super-admin rule.
* **Do not use** the older Notifier “advanced templates” article as the how-to for this console.
* Full permission matrix, exact Settings sidebar, and character caps beyond the **512**-character name are **not** locked. Follow Meta’s template policies for content. Whatsable does not publish a separate body character cap on this page.

***

## Related

<CardGroup>
  <Card title="Broadcasts (CSV)" href="/guides/notifyer-system/broadcasts">
    Send an approved template to a list. Not the create flow.
  </Card>

  <Card title="API: get templates" href="/guides/notifyer-system/api/get-templates">
    List templates and status for the connected number.
  </Card>

  <Card title="API: send a template" href="/guides/notifyer-system/api/template-message">
    One recipient, with body variables, after approval.
  </Card>

  <Card title="API: non-template message" href="/guides/notifyer-system/api/non-template-message">
    Free-form send inside the 24-hour window only.
  </Card>

  <Card title="Plans" href="/guides/notifyer-system/plans-bulk-message-pro-agency">
    Bulk Message, Pro, and Agency. Template management is on all three.
  </Card>

  <Card title="monday.com" href="/guides/notifyer-system/monday-overview">
    Send Template lists approved templates only.
  </Card>

  <Card title="Connect WhatsApp (Coexistence)" href="/guides/whatsable/connect-whatsapp-coexistence">
    Connect the number before you submit templates.
  </Card>

  <Card title="Pricing" href="https://whatsable.app/pricing">
    Plan price and unique contacts. Meta fees are separate, at 0% markup.
  </Card>
</CardGroup>

***

## FAQ

### Who can create a template in Whatsable?

Only a **super-admin**. A normal admin cannot. Template management itself is on **Bulk Message**, **Pro**, and **Agency**; the block is the role, not the plan.

### Where do I create and check templates?

**Settings → Templates** in the Whatsable console. Send dropdowns list **approved** templates only.

### How long does Meta approval take?

Usually a few minutes, sometimes up to about **24 hours**. That is the usual range, not an SLA. Recheck **Settings → Templates**. Do not keep submitting the same name while you wait.

### Can I edit a template after I submit it?

No. Create a new template and submit that. You can delete the old one. Open **preview** on the old template to copy its text. The same rule applies when Meta **rejects** one.

### Why did my template disappear from the send list?

It is not **approved** yet, or you are looking at a **different WhatsApp number**. Approvals belong to the number they were submitted on. Changing numbers means recreating every template.

### What variables can I put in the body?

Numbered placeholders `{{1}}`, `{{2}}`, … in order, each with an example for review. At send time those map to `body1`, `body2`, and so on. Do not use `{{name}}`-style names for this console.

### Why does a test send say “unsupported post request”?

Most often that **this** template is still pending. Confirm status under **Settings → Templates**. If it is approved and the error continues, treat it as a disconnected number and reconnect.

### Can I save a draft or test-send to an Ireland number from this page?

Not documented here. Use an **approved** template in broadcasts, the inbox, or the API when you need to see a real send.


# Monday.com
Source: https://docs.whatsable.app/guides/notifyer-system/monday-overview

Learn how to seamlessly integrate Monday.com with the Notifyer System for automated WhatsApp messaging directly inside your boards

# Notifyer System Integration with Monday.com

<Frame>
  <img alt="Monday.com integration with Notifyer System" />
</Frame>

<Tip>
  This guide walks you through connecting Notifyer System with Monday.com to create powerful automated WhatsApp messaging workflows — syncing conversations to your boards and triggering messages from board events, all through Monday's built-in Workflow Builder.
</Tip>

## Prerequisites

Before getting started, make sure you have:

<CardGroup>
  <Card title="Notifyer System Account" icon="user">
    Active Notifyer System account with a connected WhatsApp number and subscription plan (Pro or Agency)
  </Card>

  <Card title="Monday.com Account" icon="user">
    Access to [Monday.com](https://monday.com/) with admin or member-level permissions
  </Card>
</CardGroup>

<Info>
  Your WhatsApp number must already be connected inside Notifyer before starting the Monday integration.
</Info>

<Tip>
  New to Notifyer System? [Sign up here](https://console.notifyer-systems.com/)
</Tip>

## Setting up your Notifyer System account

<Steps>
  <Step title="Complete the Embedding Process">
    Before sending WhatsApp messages, you must complete the platform [embedding process](/guides/notifyer-system/embedding-process), which connects your WhatsApp Business account to Notifyer System.

    <Info>
      The embedding process is required by Meta to ensure proper business verification and compliance with WhatsApp Business Platform policies.
    </Info>
  </Step>

  <Step title="Set up message templates">
    To use the **Send Template Message** action in Monday workflows, configure your templates in Notifyer first. Notifyer System provides two methods for sending WhatsApp messages:

    <Accordion title="Option A: Template messages">
      <p>WhatsApp templates are pre-approved message formats that allow for personalization while maintaining compliance with WhatsApp policies.</p>

      <Steps>
        <Step title="Navigate to Templates">
          Go to **Your Templates** in your Notifyer dashboard
        </Step>

        <Step title="Create Template">
          Click the **Create Template** tab at the top of the page
        </Step>

        <Step title="Fill out the form">
          Complete the template creation form with the following details:

          <ResponseField name="Template Name" type="string">
            Choose a descriptive name for internal reference
          </ResponseField>

          <ResponseField name="Language" type="string">
            Choose your template's primary language
          </ResponseField>

          <ResponseField name="Category" type="string">
            Select the appropriate message category
          </ResponseField>

          <ResponseField name="Header" type="image | document | video">
            Optional: Add an image, document, or video header
          </ResponseField>

          <ResponseField name="Message Body" type="string">
            Craft your message content
          </ResponseField>

          <ResponseField name="Variables" type="string">
            Add placeholders using `{{1}}`, `{{2}}` format for personalization
          </ResponseField>

          <ResponseField name="Buttons" type="button">
            Optional: Configure call-to-action buttons
          </ResponseField>
        </Step>

        <Step title="Submit for review">
          Click **Preview and Submit**
        </Step>
      </Steps>

      <Frame>
        <img alt="Template Creation Interface" />
      </Frame>

      <Warning>
        Templates typically get reviewed within 24 hours. Creating compliant templates that avoid promotional language increases approval chances.
      </Warning>
    </Accordion>

    <Accordion title="Option B: Non-template messages">
      <p>For simpler communications within the 24-hour window, you can send non-template messages that include:</p>

      <CardGroup>
        <Card title="Text" icon="message-text">
          Plain text messages within the 24-hour window
        </Card>

        <Card title="Images" icon="image">
          Photos and graphics in supported formats
        </Card>

        <Card title="Documents" icon="file-pdf">
          PDFs, Word docs, and other file types
        </Card>

        <Card title="Videos" icon="video">
          MP4 and other supported video formats
        </Card>
      </CardGroup>

      <Note>
        Non-template messages can only be sent within the 24-hour customer service window after a customer initiates contact with your business.
      </Note>
    </Accordion>
  </Step>
</Steps>

## Connect Notifyer System to Monday.com

Now that your Notifyer System account is configured, follow these steps to connect Monday.com and start building workflows.

<Steps>
  <Step title="Open the Monday integration page">
    1. Log in to your **Notifyer Console**
    2. In the left sidebar, scroll to the **Connect To** section
    3. Click **Monday** from the list of available integrations (Make, Zapier, n8n, Pipedrive, Monday)

    <Frame>
      <img alt="Monday option in the Notifyer sidebar under Connect To" />
    </Frame>

    The Monday integration page opens with the **Get Started in 3 Simple Steps** panel.
  </Step>

  <Step title="Install Whatsable on Monday">
    1. On the integration page, click the green **Install Whatsable** button next to Step 1
    2. You will be redirected to the Monday.com marketplace listing
    3. Follow Monday's standard installation flow to add Whatsable to your workspace

    <Frame>
      <img alt="Install Whatsable button on the Monday integration page" />
    </Frame>

    <Tip>
      If you are already logged into Monday.com in your browser, the installation proceeds directly. Otherwise, Monday will prompt you to log in first.
    </Tip>
  </Step>

  <Step title="Log in and authorize Whatsable">
    1. Sign in to Monday.com using **Email and password**, **Google**, or **Microsoft**
    2. Review the permission consent screen titled **Authorize Whatsable — WhatsApp Automation with AI**
    3. Click **Authorize** to grant the required permissions

    <Frame>
      <img alt="Monday authorization permissions screen for Whatsable" />
    </Frame>

    Whatsable requests the following permissions exclusively for workflow automation:

    | Permission | Purpose |
    | - | - |
    | Modify any of your boards' data | Create and update items on your boards |
    | Read user's documents | Access documents for workflow actions |
    | Modify user's documents | Attach files and notes to board items |
    | Read all of your workspaces data | Access the correct workspace for automation |
    | Modify any of your workspaces data | Configure automation within your workspace |
    | Read the profile information of the users in your account | Identify users in workflow context |
    | Modify the profile information of the users on the account | Update user-related workflow data |
    | Read general information about your account | Link your Monday account to Whatsable |
    | Send notifications on your behalf | Deliver workflow-triggered notifications |
    | Post or edit updates on your behalf | Add message activity to board items |
    | Read updates and replies that you can see | Sync conversation context to workflows |
    | Read information of files that were uploaded to your account | Access attachments for board sync |
    | Read your account's tags | Map labels and tags in workflow logic |
    | Read information about teams in your account | Route workflows by team context |
    | Create and modify teams in your account | Configure team-based automation |
    | Create and modify webhooks | Enable real-time workflow triggers |
    | Read existing webhooks configuration | Verify and manage webhook setup |
    | Read your profile information | Identify the connected user |

    <Warning>
      Whatsable is an official Meta Tech Provider and the integration is safe to authorize.
    </Warning>
  </Step>

  <Step title="Confirm the connection">
    After authorization, you will be redirected back to the Notifyer Console. The green **Successfully Connected to Monday** banner confirms the integration is live.

    <Frame>
      <img alt="Successfully Connected to Monday confirmation screen" />
    </Frame>

    The panel displays your **User ID**, **Account ID**, and **Connected** timestamp. You can now start building workflows in Monday's Workflow Builder.

    <Check>
      Your Notifyer System account is now linked to Monday.com. Proceed to create workflows using the triggers and actions below.
    </Check>
  </Step>
</Steps>

## Workflow automation

With the integration connected, Whatsable exposes **3 triggers** and **2 actions** directly inside Monday's Workflow Builder.

### What you can do

<CardGroup>
  <Card title="Sync leads to boards" icon="user-plus">
    Create a Monday item automatically when a new WhatsApp contact messages your business
  </Card>

  <Card title="Keep items in sync" icon="arrows-rotate">
    Update existing items when follow-up messages are sent or received
  </Card>

  <Card title="Trigger from status" icon="arrow-right">
    Send WhatsApp template messages when board item status changes
  </Card>

  <Card title="Map WhatsApp data" icon="table-columns">
    Map phone number, country, label, AI state, attachments, and timestamps to board columns
  </Card>
</CardGroup>

### Triggers

Triggers define *when* a workflow fires.

#### Trigger 1 — When New Incoming Chat Received

**Fires:** Once, the first time an unknown contact sends your business a WhatsApp message.

This trigger activates when a message arrives from a phone number that does not yet exist as a recipient in your Whatsable system. If the contact already exists, this trigger will not fire again.

<Frame>
  <img alt="Whatsable trigger: When you receive a WhatsApp message from a new phone number" />
</Frame>

**Best for:** Creating a new Monday item (lead, support ticket, customer record) the moment a brand-new contact reaches out.

**Output fields:**

| Field | Type | Description |
| - | - | - |
| `name` | Text | Contact's display name |
| `phone` | Phone | Number in international format |
| `country` | Text | Country detected from the phone number |
| `label` | Text | Label auto-assigned by Whatsable rules |
| `message` | Text | Body of the incoming message |
| `attachment_url` | URL | Direct link to any media attachment |
| `last_message_time` | Date/Time | Timestamp of the incoming message |
| `ai_enabled` | Boolean | Whether the AI agent is active for this chat |
| `automation_note` | Text | Note injected by an upstream automation rule |

<Note>
  `sent_by` and `is_incoming` are not available on this trigger — the message is always incoming by definition.
</Note>

***

#### Trigger 2 — When New Outgoing Chat Created

**Fires:** Once, the first time you send a WhatsApp message to a contact that does not yet exist in your Whatsable system.

This trigger activates when your team initiates a conversation with a brand-new contact, whether via Whatsable's chat interface, Make, Zapier, n8n, or any connected platform.

<Frame>
  <img alt="Whatsable trigger: When you send a message to a new WhatsApp contact" />
</Frame>

**Best for:** Automatically logging a Monday item when your sales team reaches out to a new prospect.

**Output fields:**

| Field | Type | Description |
| - | - | - |
| `name` | Text | Contact's display name (may be blank if not yet resolved) |
| `phone` | Phone | Contact's phone number |
| `country` | Text | Detected country |
| `label` | Text | Label assigned to the contact |
| `message` | Text | Body of the outgoing message |
| `attachment_url` | URL | Link to any attached media |
| `last_message_time` | Date/Time | Timestamp of the outgoing message |
| `sent_by` | Text | Sender name — team member or automation/app name |
| `ai_enabled` | Boolean | Whether the AI agent is active |
| `automation_note` | Text | Note from an automation rule, if applicable |

<Note>
  `is_incoming` is not available on this trigger — the message is always outgoing by definition.
</Note>

***

#### Trigger 3 — When New Message Received or Sent in WhatsApp

**Fires:** Every time, for every message — both incoming and outgoing — for any contact, new or existing.

Unlike Triggers 1 and 2, this trigger is not limited to first-time contacts. It fires on every message event, making it ideal for keeping Monday items continuously in sync with live conversations.

<Frame>
  <img alt="Whatsable trigger: When you receive or send any WhatsApp message" />
</Frame>

**Best for:** Updating an existing Monday item's status, last message time, or activity log every time a conversation progresses.

**Output fields:**

| Field | Type | Description |
| - | - | - |
| `name` | Text | Contact's display name |
| `phone` | Phone | Contact's phone number |
| `country` | Text | Detected country |
| `label` | Text | Assigned label |
| `message` | Text | Message body |
| `attachment_url` | URL | URL of any media attachment |
| `last_message_time` | Date/Time | Message timestamp |
| `sent_by` | Text | Sender identifier (outgoing messages only) |
| `is_incoming` | Boolean | `true` if received, `false` if sent |
| `ai_enabled` | Boolean | AI agent state |
| `automation_note` | Text | Automation-injected note, if any |

<Tip>
  Map `is_incoming` to a **Checkbox** column in Monday to visually distinguish customer messages from agent replies at a glance.
</Tip>

***

#### Trigger quick reference

| Trigger | Fires for existing contacts? | Fires multiple times? | Direction |
| - | - | - | - |
| New Incoming Chat Received | No | First time only | Inbound |
| New Outgoing Chat Created | No | First time only | Outbound |
| New Message Received or Sent | Yes | Every message | Both |

**Rule of thumb:** Use Triggers 1 and 2 for contact *creation*. Use Trigger 3 for ongoing conversation *updates*.

***

### Actions

Actions define *what happens* when a trigger fires. Whatsable provides two actions.

#### Action 1 — Send Template Message

Sends an approved WhatsApp Business template message to a contact.

<Frame>
  <img alt="Whatsable action: Send a template message" />
</Frame>

**Configuration:**

1. Select **Send Template Message** from the Whatsable action list in Workflow Builder
2. Choose the template from the dropdown — all Meta-approved templates in your WABA account are listed
3. Map each template variable (e.g. `{{1}}`, `{{2}}`) to a column value from your Monday board
4. Map the **phone number** field to your board's phone/mobile column

<Warning>
  Only Meta-approved WhatsApp Business templates appear in the dropdown. Templates pending review will not be listed.
</Warning>

#### Action 2 — Send Follow-Up Message

<Info>
  This action is currently **in development** and will be available in a future release. It will support scheduled follow-up messages with timezone-aware delivery windows.
</Info>

***

### Data field reference

**Accessing trigger data:** All trigger fields are accessible inside Monday's action configuration via the dynamic data picker. When mapping a field, click the dropdown and look for **Step 1 — \[Trigger Name]** to find Whatsable's data outputs.

**Boolean fields:** `ai_enabled` and `is_incoming` return `true` or `false`. Map these to **Checkbox** columns in Monday. They cannot be mapped to text or status columns directly.

**Attachment handling:** `attachment_url` returns a direct URL to any media file sent in the message — image, video, PDF, or audio. Map it to a **Link** column to make files accessible from the board. When mapped inside a **Create Update** action, the media appears inline in the board item's activity feed.

**`sent_by` field:** Identifies the sender of an outgoing message — `"WhatsApp App"` when typed in the WhatsApp Business app, the logged-in user's name from the Notifyer chat UI, or the automation/app name for Make, Zapier, n8n, or API. Not available on Trigger 1 (Incoming Chat). You do not need to delete the WhatsApp Business app; [coexistence](/guides/notifyer-system/embedding-process#whatsapp-coexistence) is supported.

**`automation_note` field:** Populated only when a Whatsable automation rule explicitly injects a note. Blank for manually sent messages or automations without a configured note.

***

## Workflow examples

The following examples are real working workflows you can replicate inside Monday's Workflow Builder using Whatsable triggers and actions.

***

### Example 1 — Sync Every WhatsApp Message to Your Board

**What it does:** Every time a WhatsApp message is sent or received — from any contact, new or existing — this workflow either updates the matching Monday item or creates a new one if it doesn't exist yet. This is the recommended workflow for teams who want a live, always-current view of their WhatsApp conversations inside Monday.

**Trigger:** When New Message Received or Sent in WhatsApp

**Workflow structure:**

* Step 1 — Trigger: When you receive or send any WhatsApp message
* Step 2 — Find matching item (Column: mobile)
  * Found → Step 3: Create update on the matched item
  * Not found → Step 4: Create item on the Development board
    * Step 5: Create update on the new item

<Frame>
  <img alt="Workflow: Sync Every WhatsApp Message to Your Board" />
</Frame>

**How to build it:**

<Steps>
  <Step title="Add trigger and Find Matching Item">
    1. Open **Workflow Builder** on your Monday board → **Create Workflow**
    2. Add trigger → search *Whatsable* → select **When New Message Received or Sent in WhatsApp**
    3. Add **Find Matching Item** (Monday native):
       * **Board:** your target board
       * **Column:** your phone/mobile column
       * **Value:** `{phone}` from Step 1
       * **If multiple matches:** Last Created Item
  </Step>

  <Step title="Configure Found branch">
    4. **Found** branch → Add **Create Update**:
       * **Item:** Item ID from Step 2
       * **Update body:** `{message}` from Step 1
  </Step>

  <Step title="Configure Not Found branch">
    5. **Not Found** branch → Add **Create Item**:
       * **Board:** your target board
       * Map **Name** → `{name}`, **Phone** → `{phone}`, **Country** → `{country}`, **Label** → `{label}`, **Last Message Time** → `{last_message_time}`, **AI Active** → `{ai_enabled}`
    6. Below Create Item → Add **Create Update**:
       * **Item:** Item ID from Step 4
       * **Update body:** `{message}` from Step 1
    7. Click **Publish**
  </Step>
</Steps>

**Result:** New contacts are created automatically. Returning contacts get their board item updated with every new message. The activity feed on each item becomes a full log of the conversation.

<Note>
  This workflow uses Monday's **Find Matching Item** block to prevent duplicate items. Phone numbers are matched in E.164 format (e.g. `+34612345678`) — make sure your mobile column stores numbers in the same format.
</Note>

***

### Example 2 — Log New Outbound Contacts as Monday Items

**What it does:** The moment your team sends a WhatsApp message to a contact that doesn't yet exist in Whatsable, this workflow automatically creates a Monday item on your board and logs the opening message as a board activity update.

**Trigger:** When New Outgoing Chat Created

**Workflow structure:**

* Step 1 — Trigger: When you send a message to a new WhatsApp contact
* Step 2 — Create item on the Development board
* Step 3 — Create update on the new item (Item ID from Step 2)

<Frame>
  <img alt="Workflow: Log New Outbound Contacts as Monday Items" />
</Frame>

**How to build it:**

<Steps>
  <Step title="Add trigger and Create Item">
    1. Open **Workflow Builder** → **Create Workflow**
    2. Add trigger → search *Whatsable* → select **When New Outgoing Chat Created**
    3. Add **Create Item** (Monday native):
       * **Board:** your target board
       * **Group:** your preferred group (e.g. Leads, Prospects)
       * Map **Name** → `{name}`, **Phone** → `{phone}`, **Country** → `{country}`, **Label** → `{label}`, **Sent By** → `{sent_by}`, **Last Message Time** → `{last_message_time}`, **AI Active** → `{ai_enabled}`
  </Step>

  <Step title="Add Create Update and publish">
    4. Add **Create Update**:
       * **Item:** Item ID from Step 2
       * **Update body:** `{message}` from Step 1
    5. Click **Publish**
  </Step>
</Steps>

**Result:** Every new outbound conversation your team initiates is instantly captured in Monday — complete with the contact's details and the first message your team sent. The `sent_by` field tells you which team member or automation initiated the conversation.

<Note>
  This trigger fires **only once per contact** — the first time you message them. If the contact already exists in Whatsable, this workflow will not fire. For ongoing message tracking, combine this workflow with Example 1.
</Note>

***

### Example 3 — Notify Customer via WhatsApp on Status Change

**What it does:** When a Monday item's status column changes, this workflow automatically sends the contact an approved WhatsApp template message. Use it to notify customers when their order is shipped, their ticket is resolved, their proposal is ready, or any other status-driven event.

**Trigger:** Monday native — When status changes to something

**Workflow structure:**

* Step 1 — Trigger: When status changes to \[value] (Monday native)
* Step 2 — Send a template message (Whatsable action)

<Frame>
  <img alt="Workflow: Notify Customer via WhatsApp on Status Change" />
</Frame>

**How to build it:**

<Steps>
  <Step title="Add trigger">
    1. Open **Workflow Builder** → **Create Workflow**
    2. Add trigger → use Monday's default **When status changes to something**:
       * Select your **Status** column
       * Set the value to the status that should fire the workflow (e.g. Done, Shipped, Resolved)
  </Step>

  <Step title="Add Send Template Message and publish">
    3. Add Whatsable action **Send a Template Message**:
       * Select your approved template from the dropdown
       * Map each template variable (e.g. `{{1}}`) to a board column — typically the contact's name
       * Map **Phone Number** → your board's phone/mobile column
    4. Click **Publish**
  </Step>
</Steps>

**Result:** The moment your team moves an item to the configured status, the contact automatically receives a WhatsApp message — no manual outreach required.

<Tip>
  You can create multiple versions of this workflow for different status values — one for *Shipped*, another for *Resolved*, another for *Awaiting Payment* — each sending a different approved template.
</Tip>

<Warning>
  Only **Meta-approved** WhatsApp Business templates can be sent via this action. Make sure your template is approved before publishing the workflow, or the action will fail silently.
</Warning>

***

## Example use cases

<CardGroup>
  <Card title="Lead capture" icon="user-plus">
    Automatically create Monday items when new WhatsApp contacts reach out
  </Card>

  <Card title="Support tickets" icon="ticket">
    Sync support conversations to your board and track resolution status
  </Card>

  <Card title="Order confirmations" icon="box-check">
    Send template messages when order status changes to Done
  </Card>

  <Card title="Sales follow-up" icon="user-check">
    Log outbound prospecting messages as new Monday items
  </Card>

  <Card title="Activity updates" icon="arrows-rotate">
    Keep board items in sync with every message sent or received
  </Card>

  <Card title="Appointment reminders" icon="calendar">
    Trigger WhatsApp reminders when board status changes
  </Card>
</CardGroup>

***

## Disconnecting

To remove the connection, go to **Notifyer Console → Connect To → Monday** and click the red **Disconnect Whatsable from Monday** button.

<Warning>
  Disconnecting immediately stops all active Whatsable-powered workflows in Monday. Any workflows using Whatsable triggers or actions will fail until the integration is reconnected.
</Warning>

To reconnect, repeat the connection steps above. Your existing Monday workflow configurations remain intact — only the authorization needs to be re-established.

***

## Best practices

<AccordionGroup>
  <Accordion title="Use Find Matching Item for deduplication" icon="magnifying-glass">
    Use Monday's native **Find Matching Item** block filtering on the phone column to avoid duplicate items. Match type: `equals` | Result: `last_created_item` | Branch: `found` / `not_found`
  </Accordion>

  <Accordion title="Store phone numbers in E.164 format" icon="phone">
    Whatsable returns phone numbers in E.164 format (e.g. `+34612345678`). Ensure your Monday phone column stores numbers in the same format for reliable matching.
  </Accordion>

  <Accordion title="Use templates for compliance" icon="file-lines">
    Whenever possible, use pre-approved templates for better deliverability and compliance with WhatsApp Business policies.
  </Accordion>

  <Accordion title="Test workflows before production" icon="vial">
    Always test your workflows with test phone numbers before activating them for production use.
  </Accordion>

  <Accordion title="Monitor Run History" icon="chart-line">
    Regularly check **Run History** in Monday's Workflow Builder to identify and resolve any failed runs.
  </Accordion>
</AccordionGroup>

***

## Troubleshooting

<AccordionGroup>
  <Accordion title="Install Whatsable button opens Monday but nothing happens" icon="circle-exclamation">
    <Steps>
      <Step title="Check popup blocker">
        Pop-ups may be blocked in your browser. Allow popups from your Notifyer Console URL.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Step 1 still shows incomplete after installation" icon="circle-exclamation">
    <Steps>
      <Step title="Refresh the page">
        Refresh the Notifyer Console page. It needs a reload to detect that Step 1 is complete before enabling the Authorize button.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Authorization screen shows an error" icon="circle-exclamation">
    <Steps>
      <Step title="Verify account permissions">
        Ensure you are authorizing with a Monday account that has admin or sufficient member-level permissions. Guest accounts cannot authorize third-party integrations.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Workflow triggered but no item was created" icon="circle-exclamation">
    <Steps>
      <Step title="Check contact status">
        If using Trigger 1 or 2, verify whether the contact already exists in your Whatsable system. These triggers only fire for first-time contacts. Use Trigger 3 for existing contacts.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Phone number not matching in Find Matching Item" icon="circle-exclamation">
    <Steps>
      <Step title="Verify format">
        Whatsable returns phone numbers in E.164 format (e.g. `+34612345678`). Ensure your Monday phone column stores numbers in the same format.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Template not appearing in Send Template dropdown" icon="file-exclamation">
    <Steps>
      <Step title="Check approval status">
        Only Meta-approved templates are listed. Check the template status in Notifyer under **Settings → Templates**.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="sent_by field is blank" icon="circle-exclamation">
    <Steps>
      <Step title="Understand field availability">
        `sent_by` is only populated on outgoing messages. It is always empty on Trigger 1 (Incoming Chat), and blank for incoming messages on Trigger 3.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Workflow shows Failed in Run History" icon="triangle-exclamation">
    <Steps>
      <Step title="Diagnose the failure">
        Open **Run History** in Monday's Workflow Builder. Expand the failed run to see which step errored. Common causes: unmapped required phone number field on Send Template, invalid template variables, or a deleted board column that was previously mapped.
      </Step>
    </Steps>
  </Accordion>
</AccordionGroup>

***

## Technical reference

<Expandable title="Trigger and action schemas for automation builders">
  <p>This section describes the integration's behavior in structured terms for programmatic parsing and AI-assisted automation building.</p>

  **App identifier in Monday Workflow Builder:** Search for *"Whatsable"* or *"Words"*. App category: *"Automation with AI"*.

  **Trigger schemas:**

  ```
  Trigger: when_new_incoming_chat_received
    fires_once_per_contact: true
    direction: inbound
    output_fields: name, phone, country, label, message, attachment_url,
                   last_message_time, ai_enabled, automation_note

  Trigger: when_new_outgoing_chat_created
    fires_once_per_contact: true
    direction: outbound
    output_fields: name, phone, country, label, message, attachment_url,
                   last_message_time, sent_by, ai_enabled, automation_note

  Trigger: when_new_message_received_or_sent
    fires_once_per_contact: false
    fires_on_every_message: true
    direction: both
    output_fields: name, phone, country, label, message, attachment_url,
                   last_message_time, sent_by, is_incoming, ai_enabled, automation_note
  ```

  **Action schemas:**

  ```
  Action: send_template_message
    status: available
    required_inputs: template_id, phone_number
    optional_inputs: template_variables[] (mapped from board columns)

  Action: send_follow_up_message
    status: in_development
  ```

  **Idempotency notes:**

  * Triggers 1 and 2 are inherently idempotent per contact (fire at most once per phone number)
  * Trigger 3 fires on every message event and requires explicit deduplication via the Find Matching Item pattern
</Expandable>

***

## Need help?

Our support team is ready to assist you:

<CardGroup>
  <Card title="Email support" icon="envelope" href="mailto:team@whatsable.app">
    Contact [team@whatsable.app](mailto:team@whatsable.app)
  </Card>

  <Card title="Schedule a demo" icon="calendar" href="https://tidycal.com/axelmeta/notifyer-systems-demo">
    Book a personalized walkthrough
  </Card>

  <Card title="Live chat" icon="message-dots" href="">
    Click the green chat button in the bottom right corner of the Notifyer System dashboard
  </Card>
</CardGroup>

<Info>
  For additional automation platform integrations (Make, Zapier, n8n, Pipedrive), please contact our support team or check our integration documentation.
</Info>


# What can the Whatsable n8n node send and receive?
Source: https://docs.whatsable.app/guides/notifyer-system/n8n-fields

Every Whatsable n8n node field: On new Incoming message event outputs, Send template and non-template inputs, Schedule conditions, and Update Contact.

This page is the **field dictionary** for the Whatsable community node on n8n — every unlocked trigger and action input/output you can map in a workflow. Use it when you already know you want n8n and need exact labels, types, and requiredness.

For connect steps, coexistence walkthrough, examples, and troubleshooting, use [n8n overview](/guides/notifyer-system/n8n-overview).

## Prerequisites

* **Plan:** n8n requires **Pro** or **Agency** (Bulk Message does not include integrations).
* **WhatsApp number:** Connected in Whatsable. Coexistence is supported — keep the WhatsApp Business app; phone replies can fire the trigger when outgoing is enabled.
* **n8n node:** Verified community package [`n8n-nodes-whatsable`](https://www.npmjs.com/package/n8n-nodes-whatsable) (listing: [n8n.io/integrations/whatsable](https://n8n.io/integrations/whatsable/)). Search **Whatsable** in the n8n node library, or install with `npm install n8n-nodes-whatsable` on self-hosted.
* **API key:** From the Whatsable console API Keys page. Paste that key into the Whatsable credential (core product key — not a Meta Graph token).

<Info>
  Use the **Notifyer System Incoming & Outgoing Message** credential type on the trigger when you need phone-app and inbox outgoing events, not only inbound.
</Info>

***

## At a glance

| Kind | Exact name in n8n / console |
| - | - |
| Trigger (instant) | **On new Incoming message event** (node: Incoming/outgoing WhatsApp message Trigger) |
| Action · Resource **Send Message** | **Send WhatsApp Message** → product ops **Send Message Template** / **Send Non Template Message** (console: Send template via Notifyer / Send non-template via Notifyer) |
| Action · Resource **Send Message** | **Schedule WhatsApp Message** → same product ops (template or non-template) |
| Action · Resource **Send Message** | **Manage Contact** → product op **Update Contact** (console: Update recipient) |

All Notifyer/core paths use a Whatsable API key credential. When outgoing is enabled, the same trigger also fires for outgoing messages — filter with `incoming_message`.

***

## Trigger: On new Incoming message event

**Type:** Instant · **Node display name:** Incoming/outgoing WhatsApp message Trigger · **App:** Whatsable

Fires when WhatsApp messages are received — and, with the incoming-and-outgoing credential, when they are sent. Outgoing events include replies typed in the WhatsApp Business app, the Whatsable inbox, and automations.

### Configure inputs

<ResponseField name="Credential Type" type="dropdown">
  For core Whatsable (Notifyer System):

  | Option | When to use |
  | - | - |
  | **Notifyer System Incoming Message** | Inbound only |
  | **Notifyer System Incoming & Outgoing Message** | Inbound **and** outgoing (phone app, inbox, automations) |

  Legacy Bot / Notifier credential types exist on the node for other products — this fields page documents the Notifyer System options only.
</ResponseField>

<ResponseField name="HTTP Method" type="dropdown">
  **POST** (only option).
</ResponseField>

<ResponseField name="Respond" type="dropdown">
  **Immediately** — respond as soon as the trigger fires. **When Last Node Finishes** — wait for the workflow to complete before responding.
</ResponseField>

<Info>
  Copy the trigger **Production URL** into the credential’s Production URL field when creating the Notifyer System credential (see [n8n overview](/guides/notifyer-system/n8n-overview)).
</Info>

### Output fields — contact identity

<ResponseField name="phone_number" type="text / number">
  The contact’s phone number (for example `14155552671`). May arrive as a number rather than a string.
</ResponseField>

<ResponseField name="user_id" type="text">
  Unique internal ID for this contact (UUID).
</ResponseField>

<ResponseField name="recipient_name" type="text">
  Display name for this contact in Whatsable.
</ResponseField>

<ResponseField name="labels" type="text">
  Comma-separated labels on the conversation (for example `n8n, webhook-test`).
</ResponseField>

### Output fields — message data

<ResponseField name="message_type" type="text">
  Documented values on this page: `text`, `audio`, `image`, or `document`.
</ResponseField>

<ResponseField name="incoming_message" type="boolean">
  `true` when the contact sent a message to your business; `false` when your business sent a message to the contact.
</ResponseField>

<ResponseField name="send_by" type="text">
  On outgoing messages: `"WhatsApp App"` (phone app), a teammate’s name (inbox), or an automation/app name (n8n, Make, Zapier, API, bot). Empty or omitted on incoming messages.
</ResponseField>

<ResponseField name="was_message_by_human" type="boolean">
  `true` when a person sent the message (phone app or inbox); `false` when a bot or automation sent it.
</ResponseField>

<ResponseField name="attachment_url" type="text">
  Public URL of any attached file, or empty/`null` when there is none.
</ResponseField>

<ResponseField name="referral" type="object">
  Present when the inbound message came from a Click-to-WhatsApp ad or post. Typically on the **first** inbound after the tap; later messages usually omit it. Nested keys:

  | Key | Meaning |
  | - | - |
  | `source_type` | `"ad"` or `"post"` |
  | `source_id` | Ad or post ID |
  | `source_url` | Where they tapped |
  | `headline` / `body` | Ad copy |
  | `media_type` | `"image"` or `"video"` |
  | `image_url` / `video_url` | Creative URLs |
  | `ctwa_clid` | Click ID for Meta Conversions API |

  Persist `ctwa_clid` and `source_id` as soon as you see them. See also [Incoming message — Click-to-WhatsApp ads](/guides/notifyer-system/api/incoming-message#click-to-whatsapp-ads).
</ResponseField>

### Output fields — conversation history

<ResponseField name="last_messages" type="text">
  JSON string of recent messages (about the last 20). Each item includes `type` (`user` / `bot`), `content`, `timestamp`, and `content_type`. Parse before iterating.
</ResponseField>

<ResponseField name="last_message_of_user" type="text">
  The most recent message from the contact.
</ResponseField>

<ResponseField name="last_message_of_bot" type="text">
  The most recent message your business sent (human or automation).
</ResponseField>

<ResponseField name="user_last_message_time" type="number">
  Timestamp of the contact’s last message.
</ResponseField>

<ResponseField name="bot_last_message_time" type="number">
  Timestamp of your business’s last message to this contact.
</ResponseField>

<ResponseField name="conversation_paragraph" type="text">
  Flat, readable conversation history — useful for LLM prompts without parsing `last_messages`.
</ResponseField>

### Output fields — AI context and automation

<ResponseField name="note" type="text">
  AI context note stored on this contact. Update it with **Update Contact**.
</ResponseField>

<ResponseField name="note_automation" type="text">
  Automation instructions for the AI based on conversation events.
</ResponseField>

<Tip>
  Use an IF or Switch node on `incoming_message`, `send_by`, and `was_message_by_human` to split incoming vs outgoing and human phone-app replies vs automations. For rapid multi-message bursts before an AI step, add a short **Wait** node so n8n can coalesce messages from the same number into one coherent run.
</Tip>

***

## Action: Send WhatsApp Message (template or non-template)

**App:** Whatsable · **Resource:** Send Message · **Operation:** Send WhatsApp Message

Sends a WhatsApp message using the official WhatsApp API. After you pick the operation, choose **Product Operation**: **Send Message Template** (console / overview: **Send template via Notifyer**) or **Send Non Template Message** (console / overview: **Send non-template via Notifyer**).

### Mode A — Send Message Template (to start conversation)

Use this to initiate a new conversation or reach out proactively. Requires a Meta-approved template.

<ResponseField name="Phone Number" type="text">
  Recipient with country code (for example `+14155552671`) or map from a previous node. Prefer digits with country code as shown in the live editor.
</ResponseField>

<ResponseField name="Template Name or ID" type="dropdown">
  Select from your approved templates. If n8n switches the field to Expression mode on first open, click **Fixed** to return to the dropdown.
</ResponseField>

<ResponseField name="Template Variables / Body N" type="text">
  One field per template variable (`{{1}}`, `{{2}}`, … / Body 1, Body 2, …). Required when the template has variables. Media header URL and Visit Website URL appear when the selected template needs them.
</ResponseField>

<ResponseField name="Note" type="text">
  AI / internal context about this contact. Stored on the contact — **not** sent to the recipient.
</ResponseField>

<ResponseField name="Label Names or IDs" type="multiselect">
  Labels to apply to this conversation.
</ResponseField>

### Mode B — Send Non Template Message (person must write to you first)

Only inside Meta’s customer service window after the contact’s last inbound message. Outside that window, use an approved template.

<ResponseField name="Recipient Phone Number" type="text">
  Phone number with country code.
</ResponseField>

<ResponseField name="Message Type" type="dropdown">
  **Text Message**, **Image Message**, **Video Message**, **Document Message**, or **Audio Message**. Nested fields:

  | Message Type | Nested fields |
  | - | - |
  | Text Message | **Message Content** (text, required); **Enable Link Preview** (boolean, optional) |
  | Image Message | **Image URL** (url, required); **Caption** (text, optional) |
  | Video Message | **Video URL** (url, required); **Caption** (text, optional) |
  | Document Message | **Document URL** (url, required); **Caption** (text, optional); **Filename** (text, **required**) |
  | Audio Message | **Audio URL** (url, required) |
</ResponseField>

<ResponseField name="Label Names or IDs" type="multiselect">
  Labels to apply to this conversation.
</ResponseField>

<ResponseField name="Note" type="text">
  AI context note for this contact.
</ResponseField>

<Warning>
  Testing this action sends a **real** WhatsApp message. Use a personal test number during setup. Media URLs must be publicly accessible.
</Warning>

***

## Action: Schedule WhatsApp Message

**App:** Whatsable · **Resource:** Send Message · **Operation:** Schedule WhatsApp Message

Schedules a WhatsApp message for later (template or non-template product operation), with optional reply and label conditions so it can cancel or skip when the lead is already engaged.

Message fields are the same as **Send WhatsApp Message** (template or non-template, including phone, template/variables or message type, Note, and labels), **plus** the schedule and condition fields below.

### When to send — Relative (delay from now)

Set **Schedule Type : Relative or Specific** to relative (off / false).

<ResponseField name="Number" type="select">
  Choose only: **1, 2, 3, 4, 5, 10, 15, 20, 30, 60, 90, or 120**.
</ResponseField>

<ResponseField name="Unit of Time" type="select">
  **Minutes**, **Hours**, or **Days**.
</ResponseField>

### When to send — Specific date and time

Set **Schedule Type : Relative or Specific** to specific (on / true).

<ResponseField name="Scheduled Date and Time" type="datetime">
  Exact send time — map from a previous step or enter a fixed value.
</ResponseField>

<ResponseField name="Timezone" type="select">
  Timezone for the scheduled time (global list in the n8n node).
</ResponseField>

### Recipient Reply Status : Send Only If

Optional but recommended. Cancels or skips the scheduled send if the contact replies within the chosen rule.

| Condition label |
| - |
| Recipient Did Not Reply After My Last Message *(recommended default)* |
| Recipient Never Replied to Any of My Messages |
| Recipient Did Not Reply Within 20 Minutes After My Last Message |
| Recipient Did Not Reply Within 45 Minutes After My Last Message |
| Recipient Did Not Reply Within 3 Hours After My Last Message |
| Recipient Did Not Reply Within 6 Hours After My Last Message |
| Recipient Did Not Reply Within 12 Hours After My Last Message |
| Recipient Did Not Reply Within 24 Hours After My Last Message |
| Recipient Did Not Reply Within 48 Hours After My Last Message |
| Recipient Did Not Reply Within 72 Hours After My Last Message |

### Label Status : Include or Exclude (optional)

<ResponseField name="Label Status : Include or Exclude" type="select">
  **Include** — only send if the contact has this label at send time. **Does Not Include** — only send if they do not.
</ResponseField>

<ResponseField name="Label Names or IDs" type="multiselect">
  Label(s) evaluated when the scheduled send time arrives.
</ResponseField>

<Warning>
  This is **not** a native drip builder inside Whatsable. Day-0 / day-3 / day-6 sequences are multiple n8n steps that each schedule one message. Whatsable sends each scheduled message; the sequence logic lives in n8n.
</Warning>

<Note>
  The live overview also shows an optional **Schedule Message** control on immediate Send flows. Prefer the dedicated **Schedule WhatsApp Message** operation when you need relative delay, reply conditions, or label conditions.
</Note>

***

## Action: Manage Contact → Update Contact

**App:** Whatsable · **Resource:** Send Message · **Operation:** Manage Contact · **Product Operation:** Update Contact\
(Console module name: **Update recipient**)

Updates a contact in Whatsable — AI note and labels. Lookup is by phone.

### Documented fields

<ResponseField name="Phone Number Name or ID" type="dropdown">
  Lookup key — choose from the loaded phone list or map an ID/expression. Creates or updates the contact for that number.
</ResponseField>

<ResponseField name="Add a Note" type="text">
  AI context note for this contact (name, email, preferences, language, and so on).
</ResponseField>

<ResponseField name="Add Label Names or IDs" type="multiselect">
  Labels to add. Whatsable conversation labels are the source of truth inside Whatsable.
</ResponseField>

<ResponseField name="Remove Label Names or IDs" type="multiselect">
  Labels to remove. **Remove All** (when present in the remove list) clears every label on this contact.
</ResponseField>

<Info>
  **Assign a teammate:** Chat assignment is a product capability via Zapier / Make / API / keywords / AI. The n8n **Update Contact** fields documented on this page today are Phone Number Name or ID, Add a Note, and Add/Remove Label Names or IDs — confirm any assignee control in your live editor; do not invent a field key. Operator how-to: [Chat assignment](/guides/notifyer-system/chat-assignment) and [Team inbox](/guides/notifyer-system/team-inbox).
</Info>

***

## Limits and what this does NOT do

<Warning>
  **No native drip builder.** Multi-day sequences use n8n (or Make / Zapier) schedule steps plus reply conditions — not a built-in drip product inside Whatsable.
</Warning>

<Warning>
  **No CRM ↔ Whatsable bidirectional label mirror.** Add/Remove labels update Whatsable conversation labels. They do not sync Monday/Pipedrive (or other) CRM tags as one shared store.
</Warning>

<Warning>
  **Coexistence:** Do **not** uninstall the WhatsApp Business app to “enable” API or n8n. Keep using the phone; those replies can still start workflows when outgoing is enabled.
</Warning>

* **Bulk Message** plan: no n8n / integrations — upgrade to Pro or Agency.
* **Non-template** sends only inside the customer service window after the contact’s last inbound; otherwise use a template.
* **Group messaging** via the Notifyer/core n8n path is **not** documented as LIVE on this fields page (group send on the node is a separate Whatsable Bot product path — omit as core LIVE).
* Do not invent trigger `message_type` values beyond `text`, `audio`, `image`, and `document`.
* Do not invent location or sticker send types on n8n Notifyer operations.
* Typing-indicator dots are not a documented Whatsable automation claim.
* No documented **Get delivery status** search/action on the n8n node (unlike Zapier/Make) — do not invent one.
* Do not invent Whatsable numeric RPM on this page.

***

## Related features and next steps

<CardGroup>
  <Card title="n8n overview" icon="diagram-project" href="/guides/notifyer-system/n8n-overview">
    Connect, coexistence, examples, troubleshooting
  </Card>

  <Card title="Zapier fields" icon="bolt" href="/guides/notifyer-system/zapier-fields">
    Parallel Zapier trigger/action field dictionary
  </Card>

  <Card title="Make fields" icon="diagram-nested" href="/guides/notifyer-system/make-fields">
    Parallel Make module field dictionary
  </Card>

  <Card title="Incoming message / CTWA" icon="webhook" href="/guides/notifyer-system/api/incoming-message">
    Webhook payload and Click-to-WhatsApp referral object
  </Card>
</CardGroup>

Also: [Team inbox](/guides/notifyer-system/team-inbox) · [Chat assignment](/guides/notifyer-system/chat-assignment) · [Plans](/guides/notifyer-system/plans-bulk-message-pro-agency).

***

## FAQ

### Does the n8n trigger fire when someone replies in the WhatsApp Business app?

Yes, when coexistence is enabled and you use **Notifyer System Incoming & Outgoing Message**. The node may still be labelled **On new Incoming message event**. Filter on `incoming_message` (`false`), `send_by` (for example `"WhatsApp App"`), and `was_message_by_human`.

### Can I build day-0 / day-3 / day-6 WhatsApp drips with Whatsable and n8n?

Yes, by chaining **Schedule WhatsApp Message** steps (and reply conditions) in n8n. Whatsable is not a native drip builder — the sequence logic lives in n8n.

### Does Bulk Message include n8n?

No. n8n and other integrations require **Pro** or **Agency**.

### Which fields does Update Contact document today?

**Phone Number Name or ID**, **Add a Note**, **Add Label Names or IDs**, and **Remove Label Names or IDs**. Do not invent an Assign field label for n8n.

### Is there a Get delivery status action in n8n?

Not on the documented Whatsable n8n node surface for Notifyer/core. Use Zapier **Get Delivery Status** or Make **Get delivery status** if you need that lookup, or handle delivery via webhooks/API — do not invent an n8n delivery-status operation.


# n8n
Source: https://docs.whatsable.app/guides/notifyer-system/n8n-overview

Connect Notifyer System with n8n. Trigger workflows on incoming and outgoing WhatsApp messages — including replies typed in the WhatsApp Business app. Coexistence is supported; you do not delete the app on your phone.

# Notifyer System Integration with n8n

<Frame>
  <img />
</Frame>

<Tip>
  This guide walks you through connecting Notifyer System with n8n to create automated WhatsApp workflows — including triggers that fire when someone types a reply in the WhatsApp Business app, and Click-to-WhatsApp ad referral data (`source_id`, `source_url`, `ctwa_clid`) on inbound leads.
</Tip>

<Info>
  **Meta WhatsApp Coexistence is supported on Notifyer System.** You do **not** need to delete the WhatsApp Business app or stop using the number on your phone. After Embedded Signup, the same number works in the WhatsApp Business app, the Notifyer chat inbox, and automations (Make, Zapier, n8n, API, and webhooks) at the same time.
</Info>

## Prerequisites

Before getting started, make sure you have:

<CardGroup>
  <Card title="Notifyer System Account" icon="user">
    Active Notifyer System account with a subscription plan (Monthly or Pay-as-you-go)
  </Card>

  <Card title="n8n Account" icon="user">
    Access to [n8n](https://app.n8n.cloud/login) workflow automation platform
  </Card>
</CardGroup>

<Tip>
  New to Notifyer System? [Sign up here](https://console.notifyer-systems.com/)
</Tip>

## Setting up your Notifyer System account

<Steps>
  <Step title="Complete the Embedding Process">
    Before sending WhatsApp messages, complete the [embedding process](/guides/notifyer-system/embedding-process), which connects your WhatsApp Business account to Notifyer System. You do **not** need to delete the WhatsApp Business app — [coexistence](/guides/notifyer-system/embedding-process#whatsapp-coexistence) is supported.

    <Info>
      The embedding process is required by Meta to ensure proper business verification and compliance with WhatsApp Business Platform policies.
    </Info>
  </Step>

  <Step title="Set up message templates">
    Notifyer System provides two methods for sending WhatsApp messages:

    <Accordion title="Option A: Template messages">
      <p>WhatsApp templates are pre-approved message formats that allow for personalization while maintaining compliance with WhatsApp policies.</p>

      <Steps>
        <Step title="Navigate to Templates">
          Go to **Your Templates** in your Notifyer dashboard
        </Step>

        <Step title="Create Template">
          Click the **Create Template** tab at the top of the page
        </Step>

        <Step title="Fill out the form">
          Complete the template creation form with the following details:

          <ResponseField name="Template Name" type="string">
            Choose a descriptive name for internal reference
          </ResponseField>

          <ResponseField name="Language" type="string">
            Choose your template's primary language
          </ResponseField>

          <ResponseField name="Category" type="string">
            Select the appropriate message category
          </ResponseField>

          <ResponseField name="Header" type="image | document | video">
            Optional: Add an image, document, or video header
          </ResponseField>

          <ResponseField name="Message Body" type="string">
            Craft your message content
          </ResponseField>

          <ResponseField name="Variables" type="string">
            Add placeholders using `{{1}}`, `{{2}}` format for personalization
          </ResponseField>

          <ResponseField name="Buttons" type="button">
            Optional: Configure call-to-action buttons
          </ResponseField>
        </Step>

        <Step title="Submit for review">
          Click **Preview and Submit**
        </Step>
      </Steps>

      <Frame>
        <img alt="Template Creation Interface" />
      </Frame>

      <Warning>
        Templates typically get reviewed within 24 hours. Creating compliant templates that avoid promotional language increases approval chances.
      </Warning>
    </Accordion>

    <Accordion title="Option B: Non-template messages">
      <p>For simpler communications, you can send non-template messages that include:</p>

      <CardGroup>
        <Card title="Text" icon="message-text">
          Plain text messages within the 24-hour window
        </Card>

        <Card title="Images" icon="image">
          Photos and graphics in supported formats
        </Card>

        <Card title="Documents" icon="file-pdf">
          PDFs, Word docs, and other file types
        </Card>

        <Card title="Videos" icon="video">
          MP4 and other supported video formats
        </Card>
      </CardGroup>

      <Note>
        Non-template messages can only be sent within the 24-hour customer service window after a customer initiates contact with your business.
      </Note>
    </Accordion>
  </Step>

  <Step title="Get your API key">
    To connect Notifyer System with n8n, you'll need an API key:

    1. In your Notifyer dashboard, navigate to [**API Keys**](https://console.notifyer-systems.com/api-key)
    2. Copy your unique API key
    3. Store it securely—you'll need it for the integration

    <Warning>
      Never share your API key publicly or commit it to version control systems.
    </Warning>

    <Frame>
      <img alt="API Key Location" />
    </Frame>
  </Step>
</Steps>

## Integrating with n8n

<Frame>
  <iframe title="Introducing the New Features of N8N Nodes Version 2.3.3" />
</Frame>

<Steps>
  <Step title="Set up your n8n workflow">
    1. Log in to your n8n account
    2. Create a new workflow by clicking **Create Workflow**
    3. Add a trigger node of your choice:
       * Popular triggers include Google Forms, Jotform, ClickUp, or a Schedule trigger
       * Connect and configure your trigger according to your use case

    <Accordion title="Whatsable trigger node (incoming and outgoing)">
      <Info>
        Use the Whatsable trigger so n8n runs when WhatsApp messages are **received or sent** — including replies typed in the WhatsApp Business app on your phone. Select the **incoming and outgoing** credential type so those events reach n8n, not only the Notifyer inbox.
      </Info>

      <Steps>
        <Step title="Add Whatsable trigger node">
          Follow these steps to add the Whatsable trigger node to your workflow:

          1. Click the **+** button in your workflow canvas to add a new node
          2. Search for "Whatsable" in the node library search bar
          3. Select the node displaying the official Whatsable logo
          4. From the available trigger options, choose **On new Incoming message event**. That is the node's label — when outgoing is enabled (credential **Notifyer System incoming and outgoing messages**), the same trigger also fires for outgoing messages, including replies typed in the WhatsApp Business app. Filter with `incoming_message`.

          <Frame>
            <img alt="Whatsable node selection showing trigger options" />
          </Frame>

          <Tip>
            The trigger listens for WhatsApp activity and starts your workflow. Outgoing events include messages typed in the WhatsApp Business app (`send_by`: `WhatsApp App`).
          </Tip>
        </Step>

        <Step title="Configure authentication credentials">
          Set up your Whatsable API credentials to establish a secure connection:

          **Webhook URL Configuration:**

          1. In the Whatsable Trigger node parameters, locate the **Webhook URLs** section at the top
          2. Select **Production URL** and copy the generated URL by clicking on it
          3. Store this URL securely as you'll need it for the credential setup

          <Frame>
            <img alt="Production URL selection and copy interface" />
          </Frame>

          **Credential Creation:**

          1. In the **Credential to connect with** dropdown, click **+ Create new credential**
          2. Select **Whatsable Notifyer System API** as your connection method. For phone-app and inbox replies, choose the credential that covers **Notifyer System incoming and outgoing messages**
          3. Enter your Notifyer System API key in the **API Key** field
          4. Paste the Production URL you copied earlier into the **Production URL** field
          5. Assign a descriptive name to your credential (e.g., "Whatsable Production")
          6. Click **Save** to securely store your credentials

          <Frame>
            <img alt="Whatsable credential configuration interface" />
          </Frame>

          <Note>
            Your API credentials are encrypted and stored securely. Never share your API key publicly or commit it to version control.
          </Note>
        </Step>

        <Step title="Test and activate workflow">
          Complete the setup by testing and activating your trigger:

          **Response Configuration:**

          1. In the **Respond** dropdown, select your preferred response timing:
             * **Immediately**: Responds as soon as the trigger fires
             * **When Last Node Finishes**: Waits for the entire workflow to complete before responding

          **Testing:**

          1. Click **Execute step** on the Whatsable node to run a test
          2. Verify the connection is working by checking for a success confirmation
          3. Review any error messages if the test fails and adjust your configuration accordingly

          <Check>
            Once activated, your workflow processes incoming **and** outgoing messages according to your configured logic. Use `incoming_message`, `send_by`, and `was_message_by_human` in later nodes to branch on direction and sender.
          </Check>

          <Warning>
            Remember to test your workflow thoroughly before activating it in production to ensure it behaves as expected.
          </Warning>
        </Step>
      </Steps>
    </Accordion>
  </Step>

  <Step title="Add the Notifyer System node">
    1. Click the **+** button after your trigger node
    2. Search for "Whatsable" in the nodes panel
    3. Select the node with the official Whatsable logo
    4. After selecting the Whatsable node, choose 'Send template via Notifyer' or 'Send non-template via Notifyer' as needed.

    <Frame>
      <img alt="Whatsable node selection" />
    </Frame>
  </Step>

  <Step title="Configure Notifyer System credential">
    1. In the Whatsable node **Parameters**, find the **Credential to connect with** dropdown
    2. Select **+ Create new credential**
    3. Enter your Notifyer System API key that you copied earlier
    4. Name your credential (e.g., "Notifyer Production")
    5. Click **Save** to store your credential

    <Frame>
      <img alt="Configuring Notifyer System credential" />
    </Frame>
  </Step>

  <Step title="Configure your message">
    1. In **Resource** dropdown, select **Send Message**
    2. In the **Operation** dropdown, choose **Send template via Notifyer** for template messages or **Send non‑template via Notifyer** for regular messages (only works within the 24‑hour window).
    3. Complete the required fields:

    <Tabs>
      <Tab title="Operation: Send template via Notifyer">
        <Steps>
          <Step title="Configure message">
            Complete the required fields:

            <ResponseField name="Recipient" type="string">
              Enter the recipient's phone number with country code (e.g., +14155552671) or use dynamic data from previous nodes
            </ResponseField>

            <ResponseField name="Template Name or ID" type="dropdown">
              Select from your pre-approved templates in the dropdown
            </ResponseField>

            <ResponseField name="Template message details" type="string">
              Based on your selected Template message type, fill in the required fields:

              * For text messages: Enter your message content
              * For media messages: Provide a publicly accessible URL to your file
              * Optional caption (for media files)

              <Warning>
                For all media types, ensure your file URLs are publicly accessible and match the supported file formats.
              </Warning>
            </ResponseField>

            <ResponseField name="Note" type="string">
              (Optional) Include a note in the template message for internal tracking
            </ResponseField>

            <ResponseField name="Label Names or IDs" type="dropdown">
              (Optional) Select the label(s) you created in Chat Notifyer for internal tracking
            </ResponseField>

            <ResponseField name="Schedule Message" type="selection">
              (Optional) Select the date and time to schedule when your message will be sent
            </ResponseField>
          </Step>
        </Steps>
      </Tab>

      <Tab title="Operation: Send non-template via Notifyer">
        <Steps>
          <Step title="Recipient Phone Number">
            Enter the **Phone Number** with country code
          </Step>

          <Step title="Select message type">
            Choose from the following message types:

            <CardGroup>
              <Card title="Text Message" icon="message">
                For plain text messages
              </Card>

              <Card title="Document Message" icon="file">
                For sending documents (PDF, Word, etc.)
              </Card>

              <Card title="Image Message" icon="image">
                For sending images (JPEG, PNG, etc.)
              </Card>

              <Card title="Video Message" icon="video">
                For sending videos (MP4, 3GP, etc.)
              </Card>
            </CardGroup>
          </Step>

          <Step title="Complete message details">
            Based on your selected message type, fill in the required fields:

            * For text messages: Enter your message content
            * For media messages: Provide a publicly accessible URL to your file
            * Optional caption (for media files)

            <Warning>
              For all media types, ensure your file URLs are publicly accessible and match the supported file formats.
            </Warning>
          </Step>

          <Step title="Label Names or IDs">
            (Optional) Select the label(s) you created in Chat Notifyer for internal tracking
          </Step>

          <Step title="Schedule Message">
            (Optional) Select the date and time to schedule when your message will be sent
          </Step>
        </Steps>
      </Tab>
    </Tabs>
  </Step>

  <Step title="Test and activate your workflow">
    1. Click **Test Step** on the Notifyer node to verify it's working correctly
    2. If the test is successful, you'll see a confirmation message
    3. Return to your workflow
    4. Click **Save** to save your entire workflow
    5. Toggle the **Active** switch in the top-right corner to activate your workflow

    <Check>
      Your automated messaging workflow is now operational! Whenever your trigger conditions are met, n8n will automatically send WhatsApp messages through Notifyer System.
    </Check>
  </Step>
</Steps>

## Incoming and outgoing WhatsApp messages

Notifyer delivers **both incoming and outgoing** messages to your webhook or automation trigger — including messages typed by hand in the **WhatsApp Business app** on your phone.

This is possible because Notifyer supports [Meta WhatsApp Coexistence](/guides/notifyer-system/embedding-process#whatsapp-coexistence). You keep using WhatsApp Business on your phone; those hand-typed replies still reach an external webhook and can start an automation. They are not limited to the Notifyer web inbox.

<Frame>
  <iframe title="Trigger n8n workflows with WhatsApp messages" />
</Frame>

The payload is the same whether you use [n8n](/guides/notifyer-system/n8n-overview), [Make](/guides/notifyer-system/make-overview), [Zapier](/guides/notifyer-system/zapier-overview), or a [custom webhook](/guides/notifyer-system/api/incoming-message). [Watch the walkthrough on YouTube](https://www.youtube.com/watch?v=UfW-KwS4gBI).

### Direction, sending system, and team member

Use these three fields to tell *what happened* and *who sent it*:

<ResponseField name="incoming_message" type="boolean">
  `true` when a contact sent a message **to** your business. `false` when your business sent a message **to** the contact (outgoing). Filter on this field to run logic only for one direction.
</ResponseField>

<ResponseField name="send_by" type="string">
  Which system or person sent an **outgoing** message:

  | `send_by` value | Meaning |
  | - | - |
  | `WhatsApp App` | Typed by hand in the WhatsApp Business app on a phone |
  | A team member's name (for example `Axel Meta`) | Sent from the Notifyer chat inbox by that logged-in user |
  | An automation or app name (Make, Zapier, n8n, API, bot) | Sent by that integration or bot |

  Empty or omitted on incoming messages.
</ResponseField>

<ResponseField name="was_message_by_human" type="boolean">
  `true` when a person sent the message (WhatsApp Business app or Notifyer chat inbox). `false` when a bot or automation sent it. Combine with `send_by` to see both *whether* a human sent it and *which teammate or system* did.
</ResponseField>

### Example payload: message typed on the phone

This is the JSON Notifyer POSTs when someone types a reply in the WhatsApp Business app. `incoming_message` is `false`, `send_by` is `"WhatsApp App"`, and `was_message_by_human` is `true`.

```json theme={null}
{
  "last_messages": "[{\"type\":\"bot\",\"content\":\"Hello n8n\",\"timestamp\":\"2026-08-15T12:24:47.000Z\",\"content_type\":\"text\"},{\"type\":\"user\",\"content\":\"hi\",\"timestamp\":\"2026-08-12T12:27:42.746Z\",\"content_type\":\"text\"}]",
  "conversation_paragraph": "Bot (12:24:47 PM): Hello n8n ; User (12:27:42 PM): hi",
  "phone_number": 14155552671,
  "recipient_name": "Alex Martinez",
  "user_id": "158c59e1-ea85-4d0b-b70c-65328ba67a8e",
  "last_message_of_user": "hi",
  "last_message_of_bot": "Hello n8n",
  "message_type": "text",
  "user_last_message_time": 1786722580,
  "bot_last_message_time": 1786797014,
  "attachment_url": null,
  "note": "email: alex\nName: Alex",
  "note_automation": "email: alex\nName: Alex",
  "labels": "n8n, webhook-test",
  "incoming_message": false,
  "send_by": "WhatsApp App",
  "was_message_by_human": true
}
```

<Note>
  `last_message_of_bot` is the last message **your business** sent — whether a human typed it in the WhatsApp Business app or the Notifyer inbox, or a bot/automation sent it. `last_messages` is a JSON **string** of the last \~20 messages (parse it before iterating). `phone_number` may arrive as a number rather than a string.
</Note>

When the same person sends from the Notifyer chat inbox instead of the phone app, the payload is identical except:

```json theme={null}
{
  "incoming_message": false,
  "send_by": "Axel Meta",
  "was_message_by_human": true
}
```

### Click-to-WhatsApp ad attribution

When a contact messages you after tapping a **Click-to-WhatsApp** ad (Facebook, Instagram, or WhatsApp Status), Meta includes a `referral` object on that inbound event. Notifyer forwards it in [webhook](/guides/notifyer-system/api/incoming-message#click-to-whatsapp-ads) and trigger data (n8n, Make, Zapier).

Use it to see **which ad, creative, and platform** produced the lead — then label the chat, route it, or send `ctwa_clid` back to Meta for campaign optimization.

<Note>
  `referral` is typically present on the **first inbound message** after the ad click. Later messages in the same conversation usually omit it. Persist `ctwa_clid` and `source_id` as soon as you see them.
</Note>

| Field | What it tells you |
| - | - |
| `source_type` | `"ad"` for an ad, `"post"` for an organic post |
| `source_id` | Ad or post ID — use this to group leads by creative |
| `source_url` | Where they tapped (Instagram permalink, Facebook/ad URL) |
| `headline` / `body` | Ad copy the lead saw |
| `media_type` | `"image"` or `"video"` |
| `image_url` / `video_url` | Creative asset URL |
| `ctwa_clid` | Click ID for Meta Conversions API attribution |

```json theme={null}
{
  "incoming_message": true,
  "last_message_of_user": "Quiero información",
  "referral": {
    "source_type": "ad",
    "source_id": "52540693396957",
    "source_url": "https://www.instagram.com/p/DZiVBz7gAF9/",
    "headline": "Expo Nissan",
    "body": "Aprovechá la EXPONISSAN y llevate tu nuevo Nissan Kicks Play Sense MT.",
    "media_type": "image",
    "image_url": "https://scontent.xx.fbcdn.net/v/t45.1600-4/example.jpg",
    "ctwa_clid": "AfhN-JKvx8HeFTmfB-Tu11zktQRJ-MNdMV1mwvDNxHnpYrGl-jVf3OEFhLva_MP41zYRe5ErUteWFn3v4gkkjzfIEVr9J_u8GAo3-o6DqShykM4Zsl14FcU5MyThsCoQ"
  }
}
```

If your delivery includes the Cloud API envelope instead of a flattened Notifyer payload, the same object lives at `entry[].changes[].value.messages[].referral`. Full field reference and a complete example: [Message webhooks — Click-to-WhatsApp ads](/guides/notifyer-system/api/incoming-message#click-to-whatsapp-ads).

## Example use cases

<CardGroup>
  <Card title="Order confirmations" icon="box-check">
    Send automatic order confirmations when new orders are placed
  </Card>

  <Card title="Appointment reminders" icon="calendar">
    Schedule reminders before upcoming appointments
  </Card>

  <Card title="Click-to-WhatsApp ads" icon="bullhorn">
    Read `referral.source_id`, `source_url`, and `headline` to label leads by creative and platform
  </Card>

  <Card title="Customer support" icon="headset">
    Route support inquiries to the appropriate team member
  </Card>

  <Card title="Delivery updates" icon="truck">
    Keep customers informed about their delivery status
  </Card>

  <Card title="Payment reminders" icon="credit-card">
    Send automatic payment reminders for overdue accounts
  </Card>
</CardGroup>

## Best practices

<AccordionGroup>
  <Accordion title="Test thoroughly" icon="vial">
    Always test your workflows with test phone numbers before activating them for production use.
  </Accordion>

  <Accordion title="Use templates" icon="file-lines">
    Whenever possible, use pre-approved templates for better deliverability and compliance.
  </Accordion>

  <Accordion title="Add personalization" icon="user">
    Include customer names and specific details to increase engagement and response rates.
  </Accordion>

  <Accordion title="Follow WhatsApp policies" icon="shield-check">
    Ensure all message content complies with WhatsApp Business policies to avoid account restrictions.
  </Accordion>

  <Accordion title="Monitor performance" icon="chart-line">
    Regularly check your message delivery rates in your Notifyer dashboard.
  </Accordion>
</AccordionGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Messages not sending?" icon="circle-exclamation">
    <Steps>
      <Step title="Verify API key">
        Ensure your API key is entered correctly in the n8n credentials
      </Step>

      <Step title="Check phone numbers">
        Confirm phone numbers are in the correct international format (e.g., +14155552671)
      </Step>

      <Step title="Check subscription">
        Verify your Notifyer subscription is active and has available credits
      </Step>

      <Step title="Outgoing events from the WhatsApp Business app">
        Use the trigger labelled **On new Incoming message event** with the **Notifyer System incoming and outgoing messages** credential. When outgoing is enabled, that same trigger also fires for outgoing messages. Confirm `incoming_message` is `false` and `send_by` is `WhatsApp App` when you type a test reply on your phone. You do not need to delete the WhatsApp Business app.
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Template errors?" icon="file-exclamation">
    <Steps>
      <Step title="Variable check">
        Verify all required variables are included in your template message
      </Step>

      <Step title="Format verification">
        Check that variable formats match the expected values (text, number, date, etc.)
      </Step>

      <Step title="Template name">
        Ensure you're using the correct template name exactly as it appears in your dashboard
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Media not displaying?" icon="image">
    <Steps>
      <Step title="URL access">
        Confirm your media URLs are publicly accessible (test in an incognito browser)
      </Step>

      <Step title="File format">
        Verify the file format is supported by WhatsApp
      </Step>

      <Step title="File size">
        Check that file sizes are within WhatsApp limits:

        * Images: up to 5MB
        * Videos: up to 16MB
        * Documents: up to 100MB
      </Step>
    </Steps>
  </Accordion>
</AccordionGroup>

## Need help?

Our support team is ready to assist you:

<CardGroup>
  <Card title="Email support" icon="envelope" href="mailto:team@whatsable.app">
    Contact [team@whatsable.app](mailto:team@whatsable.app)
  </Card>

  <Card title="Schedule a demo" icon="calendar" href="https://tidycal.com/axelmeta/notifyer-systems-demo">
    Book a personalized walkthrough
  </Card>

  <Card title="Live chat" icon="message-dots" href="">
    Click the green chat button in the bottom right corner of the Notifyer dashboard
  </Card>
</CardGroup>

<Info>
  For additional automation platform integrations (Make.com, Zapier, etc.), please contact our support team or check our integration documentation.
</Info>


# Pipedrive
Source: https://docs.whatsable.app/guides/notifyer-system/pipedrive-overview

Learn how to seamlessly integrate Pipedrive with the Notifyer System for automated WhatsApp messaging

# Notifyer System Integration with Pipedrive

<Frame>
  <img />
</Frame>

<Tip>
  This guide walks you through connecting Notifyer System with Pipedrive to create powerful automated WhatsApp messaging workflows for your sales and CRM processes
</Tip>

## Prerequisites

Before getting started, make sure you have:

<CardGroup>
  <Card title="Notifyer System Account" icon="user">
    Active Notifyer System account with a subscription plan (Monthly or Pay-as-you-go)
  </Card>

  <Card title="Pipedrive Account" icon="user">
    Access to [Pipedrive](https://www.pipedrive.com/) CRM platform
  </Card>
</CardGroup>

<Tip>
  New to Notifyer System? [Sign up here](https://console.notifyer-systems.com/)
</Tip>

## Setting up your Notifyer System account

<Steps>
  <Step title="Complete the Embedding Process">
    Before sending WhatsApp messages, you must complete the platform [embedding process](/guides/notifyer-system/embedding-process), which connects your WhatsApp Business account to Notifyer System.

    <Info>
      The embedding process is required by Meta to ensure proper business verification and compliance with WhatsApp Business Platform policies.
    </Info>
  </Step>

  <Step title="Set up message templates">
    Notifyer System provides two methods for sending WhatsApp messages:

    <Accordion title="Option A: Template messages">
      <p>WhatsApp templates are pre-approved message formats that allow for personalization while maintaining compliance with WhatsApp policies.</p>

      <Steps>
        <Step title="Navigate to Templates">
          Go to **Your Templates** in your Notifyer dashboard
        </Step>

        <Step title="Create Template">
          Click the **Create Template** tab at the top of the page
        </Step>

        <Step title="Fill out the form">
          Complete the template creation form with the following details:

          <ResponseField name="Template Name" type="string">
            Choose a descriptive name for internal reference
          </ResponseField>

          <ResponseField name="Language" type="string">
            Choose your template's primary language
          </ResponseField>

          <ResponseField name="Category" type="string">
            Select the appropriate message category
          </ResponseField>

          <ResponseField name="Header" type="image | document | video">
            Optional: Add an image, document, or video header
          </ResponseField>

          <ResponseField name="Message Body" type="string">
            Craft your message content
          </ResponseField>

          <ResponseField name="Variables" type="string">
            Add placeholders using `{{1}}`, `{{2}}` format for personalization
          </ResponseField>

          <ResponseField name="Buttons" type="button">
            Optional: Configure call-to-action buttons
          </ResponseField>
        </Step>

        <Step title="Submit for review">
          Click **Preview and Submit**
        </Step>
      </Steps>

      <Frame>
        <img alt="Template Creation Interface" />
      </Frame>

      <Warning>
        Templates typically get reviewed within 24 hours. Creating compliant templates that avoid promotional language increases approval chances.
      </Warning>
    </Accordion>

    <Accordion title="Option B: Non-template messages">
      <p>For simpler communications, you can send non-template messages that include:</p>

      <CardGroup>
        <Card title="Text" icon="message-text">
          Plain text messages within the 24-hour window
        </Card>

        <Card title="Images" icon="image">
          Photos and graphics in supported formats
        </Card>

        <Card title="Documents" icon="file-pdf">
          PDFs, Word docs, and other file types
        </Card>

        <Card title="Videos" icon="video">
          MP4 and other supported video formats
        </Card>
      </CardGroup>

      <Note>
        Non-template messages can only be sent within the 24-hour customer service window after a customer initiates contact with your business.
      </Note>
    </Accordion>
  </Step>

  <Step title="Connect Notifyer System with Pipedrive">
    Follow these simple steps to integrate your Pipedrive account with Notifyer System:

    <Steps>
      <Step title="Access the Integration Page">
        In your Notifyer dashboard, go to [**Connect to Pipedrive**](https://console.notifyer-systems.com/pipedrive).
      </Step>

      <Step title="Initiate the Connection">
        Click the 'Connect Pipedrive Organization' button.
      </Step>

      <Step title="Authorize Access">
        You'll be redirected to Pipedrive's authorization page. Review the permissions and click 'Authorize' to grant Notifyer System access to your Pipedrive organization.
      </Step>

      <Step title="Confirm Connection">
        After authorization, you'll be automatically redirected back to your Notifyer System dashboard. Look for the connection status showing 'Connected to Pipedrive' to confirm the integration was successful.
      </Step>
    </Steps>

    <Frame>
      <img alt="Connecting Notifyer System with Pipedrive" />
    </Frame>
  </Step>
</Steps>

## Sending WhatsApp Messages from Pipedrive

Whatsable's integration with Pipedrive allows you to send WhatsApp messages directly from your deals and contacts without leaving your CRM. This guide will walk you through the complete process.

### Verifying Prerequisites

Before sending WhatsApp messages, ensure the following requirements are met:

<CardGroup>
  <Card title="Whatsable License Status" icon="badge-check">
    Must show as **PAID**
  </Card>

  <Card title="WhatsApp Connection Status" icon="signal">
    Must show as **ACTIVE**
  </Card>

  <Card title="WhatsApp Business Account" icon="whatsapp">
    Must be properly synced with Whatsable
  </Card>
</CardGroup>

<Info>
  You can verify these settings in the Whatsable Integration section of any deal or contact.
</Info>

## Sending Messages from Deals

### Accessing the Whatsable Integration Panel

<Steps>
  <Step title="Navigate to your Pipeline">
    1. Go to your **Pipedrive Dashboard**
    2. Open your desired **Pipeline**
    3. Select a **Deal** from your pipeline
  </Step>

  <Step title="Locate the Integration Panel">
    1. On the right-hand panel, scroll down past the Summary section
    2. Find the **Whatsable Integration** section

    <Frame>
      <img alt="Whatsable Integration Panel" />
    </Frame>
  </Step>
</Steps>

### Understanding the Integration Panel

The Whatsable Integration panel displays important connection information:

<CardGroup>
  <Card title="Whatsable License Status" icon="circle-check">
    Confirms your subscription is active
  </Card>

  <Card title="Synced WhatsApp Account" icon="link">
    Shows which WhatsApp Business account is connected
  </Card>

  <Card title="WhatsApp Connection Status" icon="signal-bars">
    Indicates if your WhatsApp connection is active
  </Card>

  <Card title="Last WhatsApp Communication" icon="clock">
    Displays the date and time of the most recent message
  </Card>

  <Card title="Whatsable Chat URL" icon="arrow-up-right-from-square">
    Provides a direct link to the conversation
  </Card>
</CardGroup>

### Sending Options

Within the Whatsable Integration section, you'll find a green **"Live Chat"** button with a dropdown menu offering three options:

<CardGroup>
  <Card title="Live Chat" icon="messages">
    Opens the Whatsable chat interface directly within Pipedrive
  </Card>

  <Card title="Send Scheduled Message" icon="clock">
    Schedule a message to be sent at a specific date and time
  </Card>

  <Card title="Send Template" icon="paper-plane">
    Send a pre-configured template message immediately
  </Card>
</CardGroup>

## Option 1: Send Scheduled Message

Use this option when you want to send a message at a specific future date and time.

<Steps>
  <Step title="Open the Scheduled Message Modal">
    1. Click the dropdown next to the **Live Chat** button
    2. Select **"Send Scheduled Message"**
    3. A modal window will appear with the following fields
  </Step>

  <Step title="Configure Required Fields">
    <ResponseField name="To" type="string">
      The recipient's phone number(s) associated with the deal. This field is automatically populated from the deal's contact information.
    </ResponseField>

    <ResponseField name="From" type="string">
      Your connected WhatsApp Business account. This field is pre-filled and cannot be modified from this interface.
    </ResponseField>

    <ResponseField name="Select Template" type="dropdown">
      Choose from your pre-created message templates. These templates must be created beforehand in the **Notifyer by Whatsable** dashboard.
    </ResponseField>

    <ResponseField name="Template Variables" type="string">
      Once you select a template, all required placeholder fields will appear dynamically. Fill in each field carefully to personalize your message (e.g., customer name, appointment time, order details).
    </ResponseField>

    <ResponseField name="Scheduled Date and Time" type="datetime">
      Select the exact date and time you want the message to be sent.
    </ResponseField>

    <ResponseField name="Timezone" type="dropdown">
      Specify the timezone from which you're scheduling the message to ensure accurate delivery timing.
    </ResponseField>
  </Step>

  <Step title="Add Optional Information">
    <Expandable title="Optional Fields">
      <ResponseField name="Add a Note" type="text">
        Include an internal note for your team. This note is only visible within Pipedrive and helps with tracking and context.
      </ResponseField>

      <ResponseField name="Select Labels" type="tags">
        Assign labels to categorize and organize your communications for easier filtering and reporting.
      </ResponseField>
    </Expandable>

    <Note>
      At the top of the modal, you'll see your **most recent messages** with this contact (if any previous conversations exist), providing helpful context before sending.
    </Note>
  </Step>

  <Step title="Schedule the Message">
    1. Review all information carefully
    2. Click the **"Schedule Template"** button at the bottom of the modal
    3. Your message is now scheduled and will be sent automatically at the specified time

    <Check>
      Message successfully scheduled! It will be sent at the specified time.
    </Check>

    <Frame>
      <img alt="Schedule Template Modal" />
    </Frame>
  </Step>
</Steps>

## Option 2: Send Template (Immediate)

Use this option to send a pre-configured template message immediately without scheduling.

<Steps>
  <Step title="Open the Send Template Modal">
    1. Click the dropdown next to the **Live Chat** button
    2. Select **"Send Template"**
    3. A modal window will appear with the following fields
  </Step>

  <Step title="Configure Required Fields">
    <ResponseField name="To" type="string">
      The recipient's phone number(s) associated with the deal. This field is automatically populated from the deal's contact information.
    </ResponseField>

    <ResponseField name="From" type="string">
      Your connected WhatsApp Business account. This field is pre-filled and cannot be modified from this interface.
    </ResponseField>

    <ResponseField name="Select Template" type="dropdown">
      Choose from your pre-created message templates. These templates must be created beforehand in the **Notifyer by Whatsable** dashboard.
    </ResponseField>

    <ResponseField name="Template Variables" type="string">
      Once you select a template, all required placeholder fields will appear dynamically. Fill in each field carefully to personalize your message (e.g., customer name, product details, tracking numbers).
    </ResponseField>
  </Step>

  <Step title="Add Optional Information">
    <Expandable title="Optional Fields">
      <ResponseField name="Add a Note" type="text">
        Include an internal note for your team. This note is only visible within Pipedrive and helps with tracking and context.
      </ResponseField>

      <ResponseField name="Select Labels" type="tags">
        Assign labels to categorize and organize your communications for easier filtering and reporting.
      </ResponseField>
    </Expandable>

    <Note>
      At the top of the modal, you'll see your **most recent messages** with this contact (if any previous conversations exist), providing helpful context before sending.
    </Note>
  </Step>

  <Step title="Send the Message">
    1. Review all information carefully
    2. Click the **"Send Template"** button at the bottom of the modal
    3. Your message will be sent immediately

    <Check>
      Message sent successfully!
    </Check>

    <Frame>
      <img alt="Send Template Modal" />
    </Frame>
  </Step>
</Steps>

## Sending Messages from Contacts

The process for sending WhatsApp messages from contacts is nearly identical to sending from deals, with minor differences noted below.

### Accessing the Whatsable Integration Panel

<Steps>
  <Step title="Navigate to Contacts">
    1. Go to your **Pipedrive Dashboard**
    2. Navigate to the **Contacts** menu
    3. Select your desired **Contact**
  </Step>

  <Step title="Locate the Integration Panel">
    1. On the right-hand panel, scroll down past the Summary section
    2. Find the **Whatsable Integration** section

    <Frame>
      <img alt="Whatsable Integration Panel" />
    </Frame>
  </Step>
</Steps>

### Understanding the Integration Panel

The Whatsable Integration panel displays the same connection information as in deals:

<CardGroup>
  <Card title="Whatsable License Status" icon="circle-check">
    Confirms your subscription is active
  </Card>

  <Card title="Synced WhatsApp Account" icon="link">
    Shows which WhatsApp Business account is connected
  </Card>

  <Card title="WhatsApp Connection Status" icon="signal-bars">
    Indicates if your WhatsApp connection is active
  </Card>

  <Card title="Last WhatsApp Communication" icon="clock">
    Displays the date and time of the most recent message
  </Card>

  <Card title="Whatsable Chat URL" icon="arrow-up-right-from-square">
    Provides a direct link to the conversation
  </Card>
</CardGroup>

### Sending Options

The same three options are available:

<CardGroup>
  <Card title="Live Chat" icon="messages">
    Opens the Whatsable chat interface directly within Pipedrive
  </Card>

  <Card title="Send Scheduled Message" icon="clock">
    Schedule a message for a specific date and time
  </Card>

  <Card title="Send Template" icon="paper-plane">
    Send a template message immediately
  </Card>
</CardGroup>

<Info>
  **Key Difference**: Phone numbers are pulled from the contact's information rather than deal-specific numbers. All other fields and processes remain identical to sending from deals.
</Info>

## Best Practices

<AccordionGroup>
  <Accordion title="Verify Connection Status" icon="shield-check">
    **Before Sending Messages**

    Always check that your WhatsApp connection shows as ACTIVE before attempting to send messages to avoid delivery failures.
  </Accordion>

  <Accordion title="Review Templates" icon="file-lines">
    **Template Management**

    * Ensure your message templates are up-to-date in the Notifyer dashboard
    * Test templates with yourself before using them with customers
    * Create templates in advance for different scenarios
  </Accordion>

  <Accordion title="Double-Check Phone Numbers" icon="phone">
    **Phone Number Verification**

    * Confirm the recipient's phone number is correct
    * Verify the number includes the country code (e.g., +1 for US)
    * Update contact information if numbers are missing or incorrect
  </Accordion>

  <Accordion title="Use Labels Consistently" icon="tags">
    **Message Organization**

    * Develop a clear labeling system for easier tracking
    * Apply consistent labels across your team
    * Use labels for reporting and analytics purposes
  </Accordion>

  <Accordion title="Add Internal Notes" icon="note-sticky">
    **Documentation Best Practices**

    * Document the purpose of each message for future reference
    * Include context that will help team members understand the communication
    * Keep notes concise but informative
  </Accordion>

  <Accordion title="Review Recent Messages" icon="message-lines">
    **Maintain Context**

    * Always check conversation history before sending new messages
    * Avoid sending duplicate or redundant information
    * Ensure message continuity for better customer experience
  </Accordion>

  <Accordion title="Schedule Strategically" icon="calendar-clock">
    **Timing Considerations**

    * Consider your recipient's timezone when scheduling messages
    * Avoid sending messages during off-hours or weekends unless necessary
    * Set reminders to follow up if no response is received
  </Accordion>

  <Accordion title="Create Clear Variable Names" icon="input-text">
    **Template Creation**

    * Make placeholder fields intuitive for anyone on your team
    * Use descriptive variable names (e.g., customer\_name, order\_date)
    * Test variable population before mass sending
  </Accordion>
</AccordionGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion title="WhatsApp Connection Shows as INACTIVE" icon="circle-exclamation">
    <Steps>
      <Step title="Reconnect WhatsApp Account">
        Reconnect your WhatsApp Business account in the Whatsable dashboard
      </Step>

      <Step title="Verify Configuration">
        Verify your WhatsApp Business account is properly configured
      </Step>

      <Step title="Contact Support">
        Contact Whatsable support if the issue persists after reconnection
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="No Templates Available in Dropdown" icon="empty-set">
    <Steps>
      <Step title="Create Templates">
        Create templates in the Notifyer by Whatsable dashboard first
      </Step>

      <Step title="Check Approval Status">
        Ensure templates are approved by WhatsApp (if required for your template type)
      </Step>

      <Step title="Refresh Page">
        Refresh your Pipedrive page after creating new templates to see them appear
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Scheduled Message Not Sent" icon="clock-rotate-left">
    <Steps>
      <Step title="Check Connection Status">
        Verify your WhatsApp connection was active at the scheduled time
      </Step>

      <Step title="Verify Timezone">
        Check that the timezone was set correctly when scheduling
      </Step>

      <Step title="Review Message Logs">
        Review the message logs in Whatsable for error details and delivery status
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Phone Number Not Appearing" icon="phone-slash">
    <Steps>
      <Step title="Verify Phone Number Exists">
        Ensure the contact or deal has a valid phone number in Pipedrive
      </Step>

      <Step title="Check Format">
        Verify the phone number format includes the country code (e.g., +1234567890)
      </Step>

      <Step title="Update Contact">
        Update the contact information if the phone number is missing or incorrect
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Template Variables Not Populating" icon="brackets-curly">
    <Steps>
      <Step title="Check Variable Names">
        Ensure variable names in your template match the fields you're filling
      </Step>

      <Step title="Verify Data Source">
        Confirm the data source (contact or deal) has the required information
      </Step>

      <Step title="Test Template">
        Send a test message to yourself to verify variable population before sending to customers
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Message Delivery Failed" icon="triangle-exclamation">
    <Steps>
      <Step title="Verify Recipient Number">
        Confirm the recipient has an active WhatsApp account on that number
      </Step>

      <Step title="Check Message Content">
        Ensure your message complies with WhatsApp's business messaging policies
      </Step>

      <Step title="Review Credits">
        Verify your Whatsable account has sufficient credits or an active subscription
      </Step>

      <Step title="Contact Support">
        If issues persist, contact Whatsable support with the message details
      </Step>
    </Steps>
  </Accordion>
</AccordionGroup>

<Info>
  For more information about template creation and management, visit the Notifyer by Whatsable dashboard or contact our support team.
</Info>

## Need help?

Our support team is ready to assist you:

<CardGroup>
  <Card title="Email support" icon="envelope" href="mailto:team@whatsable.app">
    Contact [team@whatsable.app](mailto:team@whatsable.app)
  </Card>

  <Card title="Schedule a demo" icon="calendar" href="https://tidycal.com/axelmeta/notifyer-systems-demo">
    Book a personalized walkthrough
  </Card>

  <Card title="Live chat" icon="message-dots" href="">
    Click the green chat button in the bottom right corner of the Notifyer System dashboard
  </Card>
</CardGroup>

<Info>
  For additional automation platform integrations and advanced configurations, please contact our support team or check our integration documentation.
</Info>


# What are Whatsable plans Bulk Message, Pro, and Agency?
Source: https://docs.whatsable.app/guides/notifyer-system/plans-bulk-message-pro-agency

Whatsable Bulk Message, Pro, Agency: unlimited messaging within your unique-contact tier, $13/100 overage, plan gates for inbox, AI, integrations, Agency.

Whatsable has three live plans — **Bulk Message**, **Pro**, and **Agency**. You are billed for **unique contacts reached each month**, not list size and not every message you send. **Unlimited messaging within your unique-contact tier** is the billing differentiator: Whatsable does not meter message volume inside that band. Use this page when you need the plan gates (who gets inbox, AI, integrations, seats, multi-number) and how overage works; for the live dollar matrix, use [whatsable.app/pricing](https://whatsable.app/pricing).

**Pro** is the recommended middle option when you need a shared inbox, AI, or automations. **Bulk Message** fits broadcast-only teams. **Agency** fits teams that need multiple WhatsApp numbers and client workspaces.

<Tip>
  **Unlimited within your tier.** Each distinct person you reach in a billing cycle counts once toward your contact band. Follow-ups and repeats to those same contacts do not add Whatsable platform message charges; Meta WhatsApp delivery fees still apply separately at Meta’s rates.
</Tip>

## Prerequisites

* **Account:** Sign up at [dashboard.whatsable.app/signin](https://dashboard.whatsable.app/signin).
* **WhatsApp Business number:** Connected through Whatsable (Embedded Signup / Coexistence supported — keep the WhatsApp Business app; do not uninstall it after connect).
* **Money page:** Treat [https://whatsable.app/pricing](https://whatsable.app/pricing) as the canonical source for current plan prices and contact-tier bands. This docs page explains **gates and billing mechanics**, not a full price grid.
* **Plan names:** Use only **Bulk Message**, **Pro**, and **Agency**. Older materials may say Basic or Standard — those are not current public names.

<Info>
  You pay two bills: the Whatsable platform plan (unique contacts), and Meta’s WhatsApp delivery fees billed separately by Meta at Meta’s rates. Whatsable passes Meta fees through at **0% markup**. See [Meta’s platform pricing](https://business.whatsapp.com/products/platform-pricing).
</Info>

***

## How unique-contact billing works

Whatsable bills on **unique contacts reached per month**, not the size of your list and not total message volume. **Unlimited messaging within your unique-contact tier** means you can send as many Whatsable-side messages as you need to those contacts — only each new unique person that month moves the meter. The unique-contact count **resets each billing cycle**.

Contact tiers available on pricing include **500, 1,000, 1,500, 3,000, 4,000, 6,000, 8,000, and 10,000+**. Pick the band that matches how many distinct people you expect to reach that month.

**Starting prices at the 500-contact band** (monthly; confirm live on pricing):

* **Bulk Message** — from **\$19/mo**
* **Pro** — from **\$49/mo** (7-day free trial on Pro)
* **Agency** — from **\$53.90/mo**

**Annual billing** gives **2 months free** (pay for ten months, receive twelve). Toggle Annual on the pricing page for monthly-equivalent figures.

### Overage per 100 unique contacts

If you stay on your current tier and reach more unique contacts than that tier covers in a billing period, you are **not cut off** and **not auto-upgraded**. You are charged **\$13 for each additional 100 unique contacts** beyond your tier that period.

Example: Pro at 500 unique contacts (**\$49/mo**) who reaches **600** pays **\$49 + \$13**. Around **80%** of your tier, Whatsable emails you about upgrading; if you do not upgrade, overage still applies only to what you go over.

Do not confuse contact overage with extra inbox seats (**\$12 / seat / mo** on Pro and Agency).

***

## Plan matrix — what each plan includes

### Bulk Message

Built for **template campaigns and CSV / audience broadcasts** from your own WhatsApp Business number.

Includes:

* Official Meta WhatsApp Business API connection
* Unlimited messaging within your unique-contact tier
* Bulk / broadcast send (CSV / audience) with approved templates
* **Scheduled broadcasts**
* Basic delivery analytics (sent / delivered / read)
* Template management
* **1 team member**
* Email support

Does **not** include:

* 2-way shared team inbox or extra inbox seats
* AI chatbot / ProactiveBot
* Integrations and automation (Make, Zapier, n8n, Pipedrive, monday.com, Attio, REST API / webhooks as product integrations)
* Advanced analytics
* Agency sub-accounts, whitelabel, or multi-number workspaces

### Pro (recommended middle)

Everything in Bulk Message, plus collaboration and automation on **one WhatsApp number per subscription**.

Includes:

* **2-way live chat / shared team inbox**
* **AI chatbot** (answers as *your* business from mission + knowledge base)
* **ProactiveBot** silent follow-ups (Pro/Agency)
* **Scheduled broadcasts**
* **Automations & integrations:** Make, Zapier, n8n, Pipedrive, monday.com, Attio, webhooks / REST API
* Advanced analytics, labels / segmentation
* Multiple team members; **extra inbox seats** from **\$12/seat/mo**
* Priority support — WhatsApp + chat + Zoom if needed
* Free onboarding / setup help on Pro & Agency (see pricing for current offer)

### Agency

Everything in Pro, plus agency-scale surfaces:

* Sub-accounts / workspaces
* Whitelabel / custom domain
* Volume pricing
* High / unlimited seats (extra seats still available as **\$12/seat/mo** add-on)
* Multiple WhatsApp Business numbers
* Dedicated account manager — WhatsApp + chat + Zoom if needed

### Feature gates at a glance

| Capability | Bulk Message | Pro | Agency |
| - | - | - | - |
| Unlimited messaging within unique-contact tier | Yes | Yes | Yes |
| Broadcast / CSV bulk templates | Yes | Yes | Yes |
| Scheduled broadcasts | Yes | Yes | Yes |
| Shared 2-way inbox / seats | No | Yes | Yes |
| AI chatbot / ProactiveBot | No | Yes | Yes |
| Integrations (Make, Zapier, n8n, CRMs, API) | No | Yes | Yes |
| Sub-accounts / whitelabel / multi-number | No | No | Yes: up to 100 WhatsApp numbers on one Agency subscription, then \$5 for each additional number |
| Support | Email | Priority (WhatsApp, chat, Zoom if needed) | Dedicated account manager |

***

## Agency multi-number — how it works today

On Whatsable Agency, one subscription covers up to 100 connected WhatsApp phone numbers. Each additional number beyond 100 costs \$5 and is added to the same subscription. You can run all your numbers from one Whatsable login. The team inbox shows every number, and you can filter it by number. Each number can have its own AI agent, and you can limit each teammate to specific numbers. If you want to keep a client fully apart, you can give that client a separate workspace with its own login and team.

***

## Extra inbox seats (Pro and Agency)

Plan price covers the included team for that plan. Buy **extra seats** when more people need the shared inbox:

* **\$12 per seat per month** (Pro and Agency only)
* Native **Android and iOS** apps
* Mobile push **only for chats assigned to that person**
* Assignment via Zapier, Make, API, keywords in chat, or AI by conversation content

Bulk Message has **no** team inbox seats. Seat add-on is **not** the same as unique-contact overage and **not** Group Messaging (unavailable / waitlist only).

***

## Trials

* **With credit card:** 500 unique contacts free for **1 week** (Pro trial on pricing). Charged automatically after the trial unless you cancel first.
* **Without credit card:** test with up to **2 recipients** for free.
* Cancel anytime from the dashboard; cancelling before the trial ends avoids the charge.

***

## Limits and what Whatsable plans do NOT include

<Warning>
  **Not on Bulk Message:** team inbox, AI chatbot, ProactiveBot, integrations (Make / Zapier / n8n / CRMs / product API automation), Agency workspaces / multi-number.
</Warning>

* **No native drip builder.** Multi-step day-0 / day-3 / day-6 sequences are possible only by building the delay logic in **Make, Zapier, or n8n**; Whatsable sends the messages.
* **No WhatsApp typing-indicator dots** claim — Response Delay exists on the AI bot; typing dots are not a documented Whatsable surface.
* **Block rate** is visible in **Meta Business Manager**, not as a Whatsable analytics metric. Bulk Message analytics = basic sent / delivered / read; Pro/Agency = advanced.
* **Group Messaging** (\$16/group style add-on) is **unavailable** (waitlist only).
* Meta MPS and coexistence throughput are Meta-side constraints.
* Meta bills at Meta rates; Whatsable markup is **0%**.
* Older plan names **Basic** / **Standard** are not current.

***

## Related

<CardGroup>
  <Card title="Pricing (canonical money)" href="https://whatsable.app/pricing">
    Live plan prices, contact tiers, annual toggle, and pricing FAQ.
  </Card>

  <Card title="Team inbox" href="/guides/notifyer-system/team-inbox">
    Shared 2-way inbox on Pro and Agency (not Bulk Message).
  </Card>

  <Card title="AI chatbot configuration" href="/guides/notifyer-system/ai-chatbot/configuration">
    AI settings — Pro and Agency only.
  </Card>

  <Card title="Make overview" href="/guides/notifyer-system/make-overview">
    Make connect and modules — Pro and Agency only.
  </Card>

  <Card title="Zapier overview" href="/guides/notifyer-system/zapier-overview">
    Zapier connect — Pro and Agency only.
  </Card>

  <Card title="Connect WhatsApp (Coexistence)" href="/guides/whatsable/connect-whatsapp-coexistence">
    Keep the Business app while using the API; do not uninstall after connect.
  </Card>
</CardGroup>

***

## FAQ

### Do you bill by messages or by contacts?

By **unique contacts reached each month**, not messages and not list size. **Unlimited messaging within your unique-contact tier** is included on every plan — Whatsable does not charge per message inside the band. The count resets each billing cycle. Meta WhatsApp delivery fees are a separate bill.

### What if I go over my contact tier?

You are not cut off and not auto-upgraded. You pay **\$13 per additional 100 unique contacts** beyond your tier that period. Example: Pro 500 at \$49 who reaches 600 pays \$49 + \$13.

### Which plan has integrations and AI?

**Pro** and **Agency**. **Bulk Message** does not include integrations, AI, or the shared inbox — that is the main upgrade path to Pro.

### Can I run several WhatsApp numbers on one Agency plan?

Yes. Agency includes up to 100 connected numbers on one subscription, and each additional number beyond that is \$5. Your team can work every number from one inbox and filter by number.

### Are extra seats the same as overage?

No. **Seats** = **\$12/seat/mo** for more people in the Pro/Agency inbox. **Overage** = **\$13 per 100 unique contacts** beyond your tier. Bulk Message has no inbox seats.

### Where do I see exact prices for every contact band?

[https://whatsable.app/pricing](https://whatsable.app/pricing) — that page is the money source of truth. This docs page covers plan gates and billing mechanics.


# Shared Team Inbox
Source: https://docs.whatsable.app/guides/notifyer-system/team-inbox

How the 2-way WhatsApp inbox works for Pro and Agency: first open, who sees what, replying as the business, labels and notes, and AI/human handoff.

<Warning>
  The shared team inbox is available on the **Pro** and **Agency** plans. **Bulk Message does not include a 2-way inbox** — it sends one-way broadcasts and campaigns only.
</Warning>

The shared team inbox — **Notifyer Chat** in the product — is where your team reads WhatsApp conversations in real time and replies as your business. This page walks through what a new team actually sees and does in there, not just the API fields behind it.

<Accordion title="I'm on Bulk Message — where's my inbox?" icon="circle-question">
  Bulk Message doesn't include the shared 2-way inbox — it's built for one-way broadcast sending. Upgrade to Pro or Agency to get it. Once you're on Pro or Agency, **the inbox lives in the left-side menu.**
</Accordion>

<Frame>
  <img alt="Whatsable left-side menu with Inbox selected and the conversation list, number filter, and label filters visible" />
</Frame>

## First open: what you'll see

The inbox is not pre-loaded with demo content. After you connect a WhatsApp number:

* It shows **only real conversations** — no sample chats to click through.
* It's **empty** until a real customer messages you (or an import finishes — see below).

<Tip>
  If you connect the number through [Meta WhatsApp Coexistence](/guides/notifyer-system/embedding-process#whatsapp-coexistence) during Embedded Signup, you can optionally import roughly the **last 6 months** of chat history from the WhatsApp Business app. That import **can take hours** to finish. If the inbox looks emptier than expected right after connecting, that's usually the import still running — not a bug.
</Tip>

## Who sees what: access layers

Visibility in the inbox stacks in three layers, plain and simple:

<Steps>
  <Step title="Phone number">
    Which connected WhatsApp number (or numbers, on Agency) this person can work at all.
  </Step>

  <Step title="Role: Admin vs. chat-only">
    **Admin** can manage the account (billing, integrations, templates, other teammates). A **chat-only** teammate works conversations in the inbox without full account admin.
  </Step>

  <Step title="Label-scoped visibility">
    Within a number, a chat-only teammate can be further limited to only the conversations carrying certain labels — for example, only "Sales" or only "Support" chats.
  </Step>
</Steps>

<Info>
  Underneath, these map to real team roles: `Admin`, `Team Member (All Labels)`, and `Team Member` (label-scoped). See [team & roles](/guides/notifyer-system/agent-skills/setup-notifyer) for the API/Agent Skills view of the same roles.
</Info>

Labels themselves can be created, assigned, or removed from several places — not only inside the inbox: the **API**, **Agent Skills**, **Zapier**, **Make**, and the **proactive bot** can all update a contact's labels.

<Note>
  Mobile push notifications follow the same access rule: a teammate is notified only for chats they **can access** (their number + role + label scope) — not every chat on the account.
</Note>

<Frame>
  <img alt="Whatsable Team page listing members with Owner, Admin, and Member roles plus numbers and conversation access" />
</Frame>

## Collaborating inside a conversation

Open a conversation and a few things are always available to your team:

* **Reassigning a chat, in practice, means changing its labels.** There isn't a separate "assign" button today — the way ownership and routing actually happens in the inbox is by adding or removing a label on the conversation (for example, swapping "Unassigned" for a teammate's name label, or a routing label your automations watch for).
* **Let the agent reply.** In the contact panel, this toggle controls whether the AI agent sends automatic replies on that chat. When it's **off** — for example because a person replied — the bot **stops immediately**. Turn it **on** again to hand the conversation back to the agent. See [AI Chatbots](/guides/notifyer-system/ai-chatbot/overview) for bot assignment and other handoff settings.
* **A reply typed in the WhatsApp Business app also stops the bot** — it's treated as human, the same as turning off **Let the agent reply**. See [Coexistence](#coexistence-phone-and-inbox-together) below for exactly what that looks like in the inbox.

<Warning>
  If your workspace has **webhook accounts** wired up: turning off **Let the agent reply** (human takeover) pauses **webhook pings on the bot path** while the chat is in that state. It does **not** pause everything — **CRM webhooks can still fire** on that same chat. If a partner integration assumes "human mode = silence," confirm which webhook path they're listening on.
</Warning>

<Frame>
  <img alt="Whatsable inbox with an open thread, contact labels, and the Let the agent reply toggle in the contact panel" />
</Frame>

Human and automation **notes** sit in the same contact panel (use the **Internal note** tab in the composer when replying). They are not shown as a separate screenshot here.

## Labels vs. notes

These look similar but do different jobs:

<CardGroup>
  <Card title="Labels" icon="tags">
    **Organize and target.** Labels group conversations (keyword labels, interest labels, teammate/routing labels) and are also what you aim a **broadcast** at — see [Label Condition](/guides/notifyer-system/zapier-overview#schedule-a-follow-up-message) in the Zapier scheduling flow.
  </Card>

  <Card title="Notes" icon="note-sticky">
    **Give context, don't organize.** Notes come in two flavors: **automation notes** (form or Lead Ad field data pushed in via Zapier/Make so the bot has context) and **human notes** (a teammate's own written context on the contact).
  </Card>
</CardGroup>

Setting either from outside the inbox: see **Update a Contact** in [Zapier](/guides/notifyer-system/zapier-overview#update-a-contact) or [Make](/guides/notifyer-system/make-overview#update-a-contact), or `assign-label.js` / `add-note.js` in the [chat-notifyer](/guides/notifyer-system/agent-skills/chat-notifyer) Agent Skill.

<Info>
  When an automation trigger fires (Zapier, Make, n8n), it carries the current **labels** and **notes** along with the **conversation paragraph** — roughly the **last 20 messages** of that chat. See the [message webhook payload](/guides/notifyer-system/api/incoming-message#payload-fields) for the exact fields (`labels`, `note`, `note_automation`, `last_messages`).
</Info>

<Frame>
  <img alt="Whatsable Labels settings page showing label names, keyword rules, and contact counts" />
</Frame>

## AI ↔ human resume behavior

What happens after a teammate takes over from the bot:

<Steps>
  <Step title="Turn off Let the agent reply">
    The bot **stops immediately** on that chat (a person replied, or you switched it off).
  </Step>

  <Step title="History stays">
    Nothing is lost — the **full conversation history** stays exactly as it was, bot messages and all.
  </Step>

  <Step title="When the agent may reply again">
    Open **Once you reply by hand** in Settings and choose when the agent may start replying again after a hand reply — one of the three options in the next section.
  </Step>
</Steps>

<Note>
  **Once you reply by hand** controls how long the agent stays quiet after you or a teammate reply by hand, before it answers on its own again. In Settings, pick one of:

  1. **The agent stays off until someone turns it back on**
  2. **The agent resumes when the customer starts a new conversation**
  3. **The agent resumes after a set time**
</Note>

<Frame>
  <img alt="Whatsable setting Once you reply by hand with three resume options in the dropdown" />
</Frame>

## Coexistence: phone and inbox together

This is the exact, confirmed behavior when your number uses [Meta WhatsApp Coexistence](/guides/notifyer-system/embedding-process#whatsapp-coexistence) and a teammate is in the web inbox while someone replies from the **WhatsApp Business app** on the same number:

* It's the **same customer thread** in the web inbox — the sync is **real time**, not a delayed refresh.
* The reply shows as coming from the **WhatsApp Business app**, **not** a named teammate. On the [message webhook payload](/guides/notifyer-system/api/incoming-message#payload-fields): `send_by: "WhatsApp App"`, `was_message_by_human: true`, `incoming_message: false`.
* That phone reply **turns off Let the agent reply** — the native AI **stops auto-replying** on that chat, the same as switching the toggle off in the inbox.
* **Make, Zapier, and n8n do not auto-pause** just because of this. Your scenario keeps running unless you explicitly filter on the human / `"WhatsApp App"` signal — see [filtering for phone-app replies](/guides/notifyer-system/api/outbound-whatsapp-app).
* **Groups, Status, and Calls do not sync** into the web inbox — only 1:1 WhatsApp conversations do.

<Info>
  What this does **not** do: it doesn't change chat assignment, it doesn't guarantee an unread badge fires, and it doesn't require a hard refresh to see the new message. If you notice any of those, that's a bug to report, not expected behavior.
</Info>

## Agency: one number or many

If your Agency workspace manages more than one WhatsApp number, you have two ways to work them:

* **One shared view, filterable by number or by label** — your team stays in a single inbox and uses the number dropdown (for example **All numbers** or one connected line) and the **Labels** filter on the list to narrow what they see, instead of switching accounts.
* **Per-customer logins** — if you'd rather keep each client's number and team fully separate, that's supported too.

## Next steps

<CardGroup>
  <Card title="Connect a WhatsApp number" icon="whatsapp" href="/guides/notifyer-system/embedding-process">
    Complete Embedded Signup (with Coexistence support) before the inbox has any conversations to show.
  </Card>

  <Card title="AI Chatbots" icon="message-bot" href="/guides/notifyer-system/ai-chatbot/overview">
    Bot assignment, handoff keywords, and settings that work with Let the agent reply in the inbox.
  </Card>

  <Card title="Message webhooks" icon="inbox" href="/guides/notifyer-system/api/incoming-message">
    Full payload reference — `send_by`, `note`, `note_automation`, `labels`, `last_messages`.
  </Card>

  <Card title="chat-notifyer Agent Skill" icon="messages" href="/guides/notifyer-system/agent-skills/chat-notifyer">
    Script-level operations for labels, handoff, notes, and conversation history.
  </Card>
</CardGroup>


# What Zapier triggers and actions does Whatsable expose?
Source: https://docs.whatsable.app/guides/notifyer-system/zapier-fields

Every Whatsable Zapier trigger and action field: New Incoming or Outgoing WhatsApp Message, Send, Schedule Follow-Up, Update a Contact, and Get Delivery Status.

This page is the **field dictionary** for the Whatsable app on Zapier — every unlocked trigger and action input/output you can map in a Zap. Use it when you already know you want Zapier and need exact labels, types, and requiredness.

For connect steps, coexistence walkthrough, examples, and troubleshooting, use [Zapier overview](/guides/notifyer-system/zapier-overview).

## Prerequisites

* **Plan:** Zapier requires **Pro** or **Agency** (Bulk Message does not include integrations).
* **WhatsApp number:** Connected in Whatsable. Coexistence is supported — keep the WhatsApp Business app; phone replies can fire the trigger.
* **Zapier app:** Public listing **Whatsable**, slug [`whatsable-ca185063`](https://zapier.com/apps/whatsable-ca185063/integrations). Search **Whatsable** in the Zap editor.
* **API key:** From the Whatsable console API Keys page. In the Zap editor, set **Credential Type** to **Notifyer** and paste that key (core product key — not a Meta Graph token).

<Info>
  The marketplace app is **public**. A console “Connect to Zapier” deep link is onboarding only — it does not mean the app is invite-only.
</Info>

***

## At a glance

| Kind | Exact name in Zapier |
| - | - |
| Trigger (instant) | **New Incoming or Outgoing WhatsApp Message** |
| Action | **Send WhatsApp Message** |
| Action | **Schedule a Follow-Up Message** |
| Action | **Update a Contact** |
| Action | **Get Delivery Status of a Message** |

***

## Trigger: New Incoming or Outgoing WhatsApp Message

**Type:** Instant · **App:** Whatsable · Internal key: `whatsable_message_trigger`

Fires when you receive or send a WhatsApp message. You can act on incoming only, outgoing only, or both by filtering after the trigger. Outgoing events include replies typed in the WhatsApp Business app, the Whatsable inbox, and automations.

### Configure inputs

<ResponseField name="Credential Type" type="dropdown">
  Select **Notifyer**.
</ResponseField>

<ResponseField name="How to Map Trigger Data" type="dropdown">
  Leave as default unless you have a specific mapping need.
</ResponseField>

### Output fields — contact identity

<ResponseField name="phone_number" type="text / number">
  The contact’s phone number (for example `14155550187`). May arrive as a number rather than a string.
</ResponseField>

<ResponseField name="user_id" type="text">
  Unique internal ID for this contact (UUID).
</ResponseField>

<ResponseField name="recipient_name" type="text">
  Display name for this contact in Whatsable.
</ResponseField>

<ResponseField name="labels" type="text">
  Comma-separated labels on the conversation (for example `Hot Lead, Buyer Qualified`).
</ResponseField>

### Output fields — message data

<ResponseField name="message_type" type="text">
  Documented values: `text`, `audio`, `image`, or `document`.
</ResponseField>

<ResponseField name="incoming_message" type="boolean">
  `true` when the contact sent a message to your business; `false` when your business sent a message to the contact.
</ResponseField>

<ResponseField name="send_by" type="text">
  On outgoing messages: `"WhatsApp App"` (phone app), a teammate’s name (inbox), or an automation/app name. Empty on incoming messages.
</ResponseField>

<ResponseField name="was_message_by_human" type="boolean">
  `true` when a person sent the message (phone app or inbox); `false` when a bot or automation sent it.
</ResponseField>

<ResponseField name="attachment_url" type="text">
  Public URL of any attached file, or empty when there is none.
</ResponseField>

<ResponseField name="is_scheduled" type="boolean">
  `true` when this event is a scheduled delivery; `false` for real-time messages.
</ResponseField>

<ResponseField name="referral" type="object">
  Present when the inbound message came from a Click-to-WhatsApp ad or post. Typically on the **first** inbound after the tap; later messages usually omit it. Nested keys:

  | Key | Meaning |
  | - | - |
  | `source_type` | `"ad"` or `"post"` |
  | `source_id` | Ad or post ID |
  | `source_url` | Where they tapped |
  | `headline` / `body` | Ad copy |
  | `media_type` | `"image"` or `"video"` |
  | `image_url` / `video_url` | Creative URLs |
  | `ctwa_clid` | Click ID for Meta Conversions API |

  Persist `ctwa_clid` and `source_id` as soon as you see them. See also [Incoming message — Click-to-WhatsApp ads](/guides/notifyer-system/api/incoming-message#click-to-whatsapp-ads).
</ResponseField>

### Output fields — conversation history

<ResponseField name="last_messages" type="text">
  JSON string of recent messages (about the last 20). Each item includes `type` (`user` / `bot`), `content`, `timestamp`, and `content_type`. Parse before iterating.
</ResponseField>

<ResponseField name="last_message_of_user" type="text">
  The most recent message from the contact.
</ResponseField>

<ResponseField name="last_message_of_bot" type="text">
  The most recent message your business sent (human or automation).
</ResponseField>

<ResponseField name="user_last_message_time" type="number">
  Unix timestamp (milliseconds) of the contact’s last message.
</ResponseField>

<ResponseField name="bot_last_message_time" type="number">
  Unix timestamp (milliseconds) of your business’s last message to this contact.
</ResponseField>

<ResponseField name="conversation_paragraph" type="text">
  Flat, readable conversation history — useful for LLM prompts without parsing `last_messages`.
</ResponseField>

### Output fields — AI context and automation

<ResponseField name="note" type="text">
  AI context note stored on this contact. Update it with **Update a Contact**.
</ResponseField>

<ResponseField name="note_automation" type="text">
  Automation instructions for the AI based on conversation events.
</ResponseField>

<ResponseField name="scheduled_messages" type="text">
  Description of messages currently scheduled to this contact.
</ResponseField>

<Tip>
  Use a Zapier Filter on `incoming_message`, `send_by`, and `was_message_by_human` to split incoming vs outgoing and human phone-app replies vs automations.
</Tip>

***

## Action: Send WhatsApp Message

**App:** Whatsable · Internal key: `send_whatsapp_message`

Sends a WhatsApp message using the official WhatsApp API. You can add labels and write notes that appear in Whatsable’s chat interface. Choose **Configuration**: template (start a conversation / proactive) or non-template (inside the customer service window).

### Mode A — Send WhatsApp Template (to start conversation)

<ResponseField name="Phone Number" type="text">
  Recipient in international format — digits only, no `+` or spaces (for example `14155550187`).
</ResponseField>

<ResponseField name="Template Name or ID" type="dropdown">
  Select from your approved templates. The dropdown shows a live preview of body, language, and category.
</ResponseField>

<ResponseField name="Body 1, Body 2, … (variables)" type="text">
  One field per template variable (`{{1}}`, `{{2}}`, …). Required when the template has variables.
</ResponseField>

<ResponseField name="Media" type="text">
  Public URL for a media header (image, video, or document). Only when the selected template has a media header.
</ResponseField>

<ResponseField name="Visit Website URL" type="text">
  Full URL including the dynamic portion, when the template has a dynamic URL button.
</ResponseField>

<ResponseField name="Note" type="text">
  AI context about this contact. Stored on the contact — **not** sent to the recipient.
</ResponseField>

<ResponseField name="Label Names or IDs" type="multiselect">
  Labels to apply to this conversation.
</ResponseField>

### Mode B — Non-template message (person must write to you first)

Only inside Meta’s customer service window after the contact’s last inbound message. Outside that window, use an approved template.

<ResponseField name="Recipient Phone Number" type="text">
  Same digit format as Phone Number above.
</ResponseField>

<ResponseField name="Message Type" type="dropdown">
  **Text Message**, **Image Message**, **Video Message**, **Document Message**, or **Audio Message**. Nested fields:

  | Message Type | Nested fields |
  | - | - |
  | Text Message | **Message Content** (text, required); **Enable Link Preview** (boolean, optional, default false) |
  | Image Message | **Image URL** (url, required); **Caption** (text, optional) |
  | Video Message | **Video URL** (url, required); **Caption** (text, optional) |
  | Document Message | **Document URL** (url, required); **Caption** (text, optional); **Filename** (text, required) |
  | Audio Message | **Audio URL** (url, required) |
</ResponseField>

<ResponseField name="Label Names or IDs" type="multiselect">
  Labels to apply to this conversation.
</ResponseField>

<ResponseField name="Note" type="text">
  AI context note for this contact.
</ResponseField>

<Warning>
  Testing this action sends a **real** WhatsApp message. Use a personal test number during setup.
</Warning>

***

## Action: Schedule a Follow-Up Message

**App:** Whatsable · Internal key: `schedule_follow_up_message`

Schedules a WhatsApp message for later, with optional reply and label conditions so it can cancel or skip when the lead is already engaged.

Message fields are the same as **Send WhatsApp Message** (template or non-template, including phone, template/variables or message type, Note, and labels), **plus** the schedule and condition fields below.

### When to send — Relative (delay from now)

<ResponseField name="Delay Value" type="select">
  Choose only: **1, 2, 3, 4, 5, 10, 15, 20, 30, 60, 90, or 120**.
</ResponseField>

<ResponseField name="Delay Unit" type="select">
  **Minutes**, **Hours**, or **Days**.
</ResponseField>

### When to send — Specific date and time

<ResponseField name="Date & Time" type="datetime">
  Exact send time — map from a previous step or enter a fixed value.
</ResponseField>

<ResponseField name="Timezone" type="select">
  Timezone for the scheduled time (global list in the Zap editor).
</ResponseField>

### Reply Condition

Optional but recommended. Cancels the scheduled send if the contact replies within the chosen rule.

| Condition label |
| - |
| Recipient did not reply after my last message *(recommended default)* |
| Recipient never replied to any of my messages |
| Recipient did not reply within 20 minutes |
| Recipient did not reply within 45 minutes |
| Recipient did not reply within 3 hours |
| Recipient did not reply within 6 hours |
| Recipient did not reply within 12 hours |
| Recipient did not reply within 24 hours |
| Recipient did not reply within 48 hours |
| Recipient did not reply within 72 hours |

### Label condition (optional)

<ResponseField name="Label Condition" type="select">
  **Include** — only send if the contact has this label at send time. **Does Not Include** — only send if they do not.
</ResponseField>

<ResponseField name="Label" type="select">
  Label evaluated when the scheduled send time arrives.
</ResponseField>

<Warning>
  This is **not** a native drip builder inside Whatsable. Day-0 / day-3 / day-6 sequences are multiple Zap steps (or Paths) that each schedule one message. Whatsable sends each scheduled message; the sequence logic lives in Zapier.
</Warning>

***

## Action: Update a Contact

**App:** Whatsable · Internal key: `update_contact`

Updates a contact in Whatsable — display name, AI note, and labels. The Zapier action description also states you can **assign the conversation to a teammate**.

### Documented fields

<ResponseField name="Phone Number" type="text">
  Lookup key in international digit format. Creates a contact if none exists yet.
</ResponseField>

<ResponseField name="Display Name" type="text">
  Display name in the Whatsable chat interface.
</ResponseField>

<ResponseField name="Add a Note" type="text">
  AI context note for this contact (name, email, preferences, language, and so on).
</ResponseField>

<ResponseField name="Add Label Names or IDs" type="multiselect">
  Labels to add. Whatsable conversation labels are the source of truth inside Whatsable.
</ResponseField>

<ResponseField name="Remove Label Names or IDs" type="multiselect">
  Labels to remove. **Remove All** clears every label on this contact.
</ResponseField>

<Info>
  **Assign a teammate:** Update a Contact can assign the conversation to a teammate (Zapier action description + Zapier / Make / API). Documented fields on this page today are Phone Number, Display Name, Add a Note, and Add/Remove Label Names or IDs. Confirm any assignee control in your live Zap editor sample — do not rely on an undocumented field name. Operator how-to: [Chat assignment](/guides/notifyer-system/chat-assignment) and [Team inbox](/guides/notifyer-system/team-inbox).
</Info>

***

## Action: Get Delivery Status of a Message

**App:** Whatsable · Internal key: `get_message_delivery_status`

Checks whether a previously sent WhatsApp message was delivered — useful for fallback paths (for example email) when a number may be wrong or inactive.

<ResponseField name="Message ID" type="text">
  Map from the output of a prior **Send WhatsApp Message** or **Schedule a Follow-Up Message** step (`message_id` in Zapier’s data mapper).
</ResponseField>

Use the returned **status** in a Zapier Filter or Paths step to branch delivered vs not-delivered flows (for example send a fallback email).

<Note>
  If a lookup fails in Zap History, re-check the mapped Message ID and contact support if needed. Do not assume every Message ID always resolves in every environment.
</Note>

***

## Limits and what this does NOT do

<Warning>
  **No native drip builder.** Multi-day sequences use Zapier (or Make / n8n) schedule steps plus reply conditions — not a built-in drip product inside Whatsable.
</Warning>

<Warning>
  **No CRM ↔ Whatsable bidirectional label mirror.** Add/Remove labels update Whatsable conversation labels. They do not sync Monday/Pipedrive (or other) CRM tags as one shared store.
</Warning>

<Warning>
  **Coexistence:** Do **not** uninstall the WhatsApp Business app to “enable” API or Zapier. Keep using the phone; those replies can still start Zaps.
</Warning>

* **Bulk Message** plan: no Zapier / integrations — upgrade to Pro or Agency.
* **Non-template** sends only inside the customer service window after the contact’s last inbound; otherwise use a template.
* **Phone format:** digits only, full international, no `+`, spaces, or dashes.
* **Group messaging** via Zapier is **not** documented on this fields page (not an unlocked Official API docs surface here).
* Do not invent trigger `message_type` values beyond `text`, `audio`, `image`, and `document`.
* Typing-indicator dots are not a documented Whatsable automation claim.

***

## Related features and next steps

<CardGroup>
  <Card title="Zapier overview" icon="bolt" href="/guides/notifyer-system/zapier-overview">
    Connect, coexistence, examples, troubleshooting
  </Card>

  <Card title="Team inbox" icon="inbox" href="/guides/notifyer-system/team-inbox">
    Shared inbox and human replies alongside automations
  </Card>

  <Card title="Chat assignment" icon="user-check" href="/guides/notifyer-system/chat-assignment">
    Assign chats via Zapier, Make, API, keywords, or AI
  </Card>

  <Card title="Incoming message / CTWA" icon="webhook" href="/guides/notifyer-system/api/incoming-message">
    Webhook payload and Click-to-WhatsApp referral object
  </Card>
</CardGroup>

Also: [Make overview](/guides/notifyer-system/make-overview) · [n8n overview](/guides/notifyer-system/n8n-overview) · [Plans](/guides/notifyer-system/plans-bulk-message-pro-agency).

***

## FAQ

### Does the Zapier trigger fire when someone replies in the WhatsApp Business app?

Yes, when coexistence is enabled and outgoing events are included. Filter on `incoming_message`, `send_by` (for example `"WhatsApp App"`), and `was_message_by_human`.

### Can I build day-0 / day-3 / day-6 WhatsApp drips with Whatsable and Zapier?

Yes, by chaining **Schedule a Follow-Up Message** steps (and reply conditions) in Zapier. Whatsable is not a native drip builder — the sequence logic lives in Zapier.

### Does Bulk Message include Zapier?

No. Zapier and other integrations require **Pro** or **Agency**.

### Which fields does Update a Contact document today?

**Phone Number**, **Display Name**, **Add a Note**, **Add Label Names or IDs**, and **Remove Label Names or IDs**. Assigning a teammate is supported as a product capability via Zapier; confirm the live editor for any assignee control rather than inventing a field name.


# Zapier
Source: https://docs.whatsable.app/guides/notifyer-system/zapier-overview

Notifyer System triggers and actions in Zapier — incoming and outgoing WhatsApp messages, including replies typed in the WhatsApp Business app. Coexistence is supported; you do not delete the app on your phone.

# Notifyer System Integration with Zapier

<Frame>
  <img />
</Frame>

<Tip>
  This guide covers every trigger and action available for the Notifyer System inside Zapier — so you can build fully automated WhatsApp workflows that send messages, schedule follow-ups, update contacts, and react to incoming **and outgoing** messages in real time.
</Tip>

<Info>
  **Meta WhatsApp Coexistence is supported on Notifyer System.** You do **not** need to delete the WhatsApp Business app or stop using the number on your phone. After Embedded Signup, the same number works in the WhatsApp Business app, the Notifyer chat inbox, and automations (Make, Zapier, n8n, API, and webhooks) at the same time.
</Info>

## Available triggers & actions at a glance

The Notifyer System connects to Zapier through the **Whatsable** app. Once connected with your Notifyer API key, you get access to the following:

<CardGroup>
  <Card title="Trigger (Instant)" icon="bolt">
    * New Incoming or Outgoing WhatsApp Message
  </Card>

  <Card title="Actions" icon="play">
    * Send WhatsApp Message
    * Schedule a Follow-Up Message
    * Update a Contact
    * Get Delivery Status of a Message
  </Card>
</CardGroup>

<Info>
  All triggers and actions in this guide use the **Whatsable** app on Zapier. Notifyer System users connect using their **Notifyer API key**.
</Info>

***

## Prerequisites

Before getting started, make sure you have:

<CardGroup>
  <Card title="Notifyer System Account" icon="user">
    Active Notifyer System account with a subscription plan (Monthly or Pay-as-you-go) and a connected WhatsApp number
  </Card>

  <Card title="Zapier Account" icon="user">
    Access to [Zapier](https://zapier.com/sign-up/) workflow automation platform
  </Card>
</CardGroup>

<Tip>
  New to Notifyer System? [Sign up here](https://console.notifyer-systems.com/)
</Tip>

***

## Setting up your Notifyer System account

<Steps>
  <Step title="Complete the Embedding Process">
    Before sending WhatsApp messages, complete the [embedding process](/guides/notifyer-system/embedding-process), which connects your WhatsApp Business account to Notifyer System. You do **not** need to delete the WhatsApp Business app — [coexistence](/guides/notifyer-system/embedding-process#whatsapp-coexistence) is supported.

    <Info>
      The embedding process is required by Meta to ensure proper business verification and compliance with WhatsApp Business Platform policies.
    </Info>
  </Step>

  <Step title="Set up message templates (if using template messages)">
    WhatsApp templates are pre-approved message formats required to initiate a new conversation with a contact. Create and get them approved in Notifyer before using them in Zapier.

    <Accordion title="How to create a template">
      <Steps>
        <Step title="Navigate to Templates">
          Go to **Your Templates** in your Notifyer dashboard
        </Step>

        <Step title="Create Template">
          Click the **Create Template** tab at the top of the page
        </Step>

        <Step title="Fill out the form">
          <ResponseField name="Template Name" type="string">
            Choose a descriptive name for internal reference
          </ResponseField>

          <ResponseField name="Language" type="string">
            Choose your template's primary language
          </ResponseField>

          <ResponseField name="Category" type="string">
            Select the appropriate message category (Marketing, Utility, Authentication)
          </ResponseField>

          <ResponseField name="Header" type="image | document | video">
            Optional: Add an image, document, or video header
          </ResponseField>

          <ResponseField name="Message Body" type="string">
            Craft your message content. Use `{{1}}`, `{{2}}` placeholders for dynamic variables
          </ResponseField>

          <ResponseField name="Buttons" type="button">
            Optional: Configure call-to-action or quick reply buttons
          </ResponseField>
        </Step>

        <Step title="Submit for review">
          Click **Preview and Submit**
        </Step>
      </Steps>

      <Warning>
        Templates are typically reviewed within 24 hours. Utility and Authentication templates have the highest approval rates.
      </Warning>
    </Accordion>
  </Step>

  <Step title="Get your Notifyer API key">
    1. In your Notifyer dashboard, navigate to [**API Keys**](https://console.notifyer-systems.com/api-key)
    2. Copy your unique API key
    3. Store it securely — you will need it when creating the Zapier connection

    <Warning>
      Never share your API key publicly or commit it to version control systems.
    </Warning>
  </Step>
</Steps>

***

## Connect Notifyer System to Zapier

<Steps>
  <Step title="Accept the Whatsable app invitation">
    1. Log in to your Notifyer System dashboard
    2. Navigate to **Connect to Zapier** in the side menu
    3. Click **Continue** in the connection guide popup
    4. Click **Accept & Build a Zap** on the invitation page

    <Check>
      The **Whatsable** app is now available in your Zapier account. You can find it by searching "Whatsable" in any Zap editor.
    </Check>
  </Step>

  <Step title="Create a new Zap">
    1. Log in to your Zapier account at [zapier.com](https://zapier.com)
    2. Click **+ Create** and select **Zaps** (or **New Zap**)
    3. You are now in the Zap editor and ready to add your first step — follow the trigger or action setup guides in the [Step Reference](#step-reference) section below
  </Step>
</Steps>

***

## Step Reference

### Trigger

***

### New Incoming or Outgoing WhatsApp Message

<Info>
  **Type:** Instant Trigger | **App:** Whatsable | **Connection:** Notifyer API key
</Info>

**Description in Zapier:** *"When you receive or send a WhatsApp message. You can choose to only trigger this when you send or receive a message, or both."*

Fires in real time whenever a WhatsApp message event occurs in your Notifyer console. You can configure it to fire on **incoming messages only**, **outgoing messages only**, or **both directions**. Outgoing events include messages **typed by hand in the WhatsApp Business app**, messages sent from the Notifyer chat inbox, and messages sent by automations. This is the entry point for AI chatbot workflows, lead qualification, CRM syncing, and any automation that must react when a teammate replies on their phone.

***

#### Setting up the trigger

<Steps>
  <Step title="Add the trigger step">
    1. In your Zap editor, click the **Trigger** step
    2. Search for **Whatsable** in the app search bar
    3. Select **Whatsable** from the results
    4. Under **Trigger Event**, select **New Incoming or Outgoing WhatsApp Message**
    5. Click **Continue**
  </Step>

  <Step title="Connect your Notifyer account">
    1. In the **Account** section, click **Sign in to Whatsable**
    2. A dialog will appear asking for your API key — paste your **Notifyer API key**
    3. Click **Yes, Continue to Whatsable**

    <Info>
      You only need to do this once. Once your account is connected, you can reuse it across all Whatsable steps in any of your Zaps.
    </Info>

    <Warning>
      Make sure you are pasting the Notifyer API key, not the WhatsApp API key. Your Notifyer API key is found at [console.notifyer-systems.com/api-key](https://console.notifyer-systems.com/api-key).
    </Warning>
  </Step>

  <Step title="Configure the trigger">
    In the **Configure** section, you will see the following fields:

    <ResponseField name="Credential Type" type="dropdown">
      Select **Notifyer** — this tells the app you are authenticating with a Notifyer System API key
    </ResponseField>

    <ResponseField name="How to Map Trigger Data" type="dropdown">
      Choose how incoming trigger data is mapped to your Zap fields. Leave as default unless you have specific mapping requirements
    </ResponseField>

    Click **Continue** when done.
  </Step>

  <Step title="Test the trigger">
    1. Click **Test trigger** — Zapier will attempt to fetch a recent message event from your Notifyer console
    2. If a test record is found, Zapier displays a sample data payload showing all available output fields
    3. Review the fields to confirm the data looks correct

    <Tip>
      If no test data appears, send a WhatsApp message to your connected number first, then click **Test trigger** again. Zapier needs at least one recent event to pull a sample.
    </Tip>

    <Check>
      Once the test passes, your trigger is configured. Click **Continue** to add your first action step.
    </Check>
  </Step>
</Steps>

***

#### Trigger output fields

When this trigger fires, your Zap receives the following data fields from Notifyer. You can map any of these fields into your action steps.

<AccordionGroup>
  <Accordion title="Contact identity">
    <ResponseField name="phone_number" type="text">
      The phone number of the contact (e.g. `14155550187`). This is the contact who sent or received the message
    </ResponseField>

    <ResponseField name="user_id" type="text">
      Unique internal ID for this contact in Notifyer (UUID format)
    </ResponseField>

    <ResponseField name="recipient_name" type="text">
      The display name used for this contact in Notifyer
    </ResponseField>

    <ResponseField name="labels" type="text">
      Comma-separated list of labels currently applied to this conversation (e.g. `Hot Lead, Buyer Qualified, Urgent`)
    </ResponseField>
  </Accordion>

  <Accordion title="Message data">
    <ResponseField name="message_type" type="text">
      Type of the message: `text`, `audio`, `image`, or `document`
    </ResponseField>

    <ResponseField name="incoming_message" type="boolean">
      `true` when the contact sent a message to your business; `false` when your business sent a message to the contact. Use a **Filter** step after the trigger to act only on incoming or outgoing messages
    </ResponseField>

    <ResponseField name="send_by" type="text">
      Which system or person sent an outgoing message: `"WhatsApp App"` for the WhatsApp Business app, the teammate's name for the Notifyer chat inbox, or the automation/app name for Make, Zapier, n8n, or API. Empty on incoming messages
    </ResponseField>

    <ResponseField name="was_message_by_human" type="boolean">
      `true` when a person sent the message (phone app or Notifyer inbox). `false` when a bot or automation sent it
    </ResponseField>

    <ResponseField name="attachment_url" type="text">
      Public URL of any file attached to the message (image, document, audio). Empty if the message has no attachment
    </ResponseField>

    <ResponseField name="is_scheduled" type="boolean">
      `true` if this trigger was fired by a scheduled message being delivered; `false` for real-time messages
    </ResponseField>

    <ResponseField name="referral" type="object">
      Present when the inbound message came from a Click-to-WhatsApp ad or post. Includes `source_type`, `source_id`, `source_url` (platform), `headline`, `body`, `media_type`, creative URLs, and `ctwa_clid`. Omitted on ordinary chats and on most follow-up messages. See [Click-to-WhatsApp ads](/guides/notifyer-system/api/incoming-message#click-to-whatsapp-ads).
    </ResponseField>
  </Accordion>

  <Accordion title="Conversation history">
    <ResponseField name="last_messages" type="text">
      JSON array of recent messages in the conversation. Each item includes: `type` (user/bot), `content`, `timestamp`, `content_type`. Useful for passing full history to an AI model
    </ResponseField>

    <ResponseField name="last_message_of_user" type="text">
      The most recent message sent by the contact — the message that triggered this Zap run
    </ResponseField>

    <ResponseField name="last_message_of_bot" type="text">
      The most recent message your business sent to this contact — helps prevent an AI from repeating the same response
    </ResponseField>

    <ResponseField name="user_last_message_time" type="number">
      Unix timestamp (milliseconds) of when the contact's last message was received
    </ResponseField>

    <ResponseField name="bot_last_message_time" type="number">
      Unix timestamp (milliseconds) of when your business last messaged this contact
    </ResponseField>

    <ResponseField name="conversation_paragraph" type="text">
      A flat, readable version of the full conversation history — ideal for passing directly into an AI/LLM prompt without needing to parse the `last_messages` JSON array
    </ResponseField>
  </Accordion>

  <Accordion title="AI context & automation fields">
    <ResponseField name="note" type="text">
      The AI context note stored on this contact in Notifyer. Contains lead details: name, email, preferences, background, language, etc. Set or update this using the **Update a Contact** action
    </ResponseField>

    <ResponseField name="note_automation" type="text">
      Automation instructions for the AI — rules the AI follows automatically based on conversation events (e.g. "If budget confirmed and timeline under 6 months, notify the agent within 1 hour")
    </ResponseField>

    <ResponseField name="scheduled_messages" type="text">
      Description of any messages currently scheduled to be sent to this contact at a future time
    </ResponseField>
  </Accordion>
</AccordionGroup>

<Note>
  Use the `incoming_message` field with a Zapier **Filter** step to split logic between incoming messages (contacts writing to you) and outgoing messages (your business sending). Use `send_by` and `was_message_by_human` to see whether the WhatsApp Business app, a named teammate, or an automation sent it.
</Note>

## Incoming and outgoing WhatsApp messages

Notifyer delivers **both incoming and outgoing** messages to your webhook or automation trigger — including messages typed by hand in the **WhatsApp Business app** on your phone.

This is possible because Notifyer supports [Meta WhatsApp Coexistence](/guides/notifyer-system/embedding-process#whatsapp-coexistence). You keep using WhatsApp Business on your phone; those hand-typed replies still reach an external webhook and can start an automation. They are not limited to the Notifyer web inbox.

<Frame>
  <iframe title="Trigger n8n workflows with WhatsApp messages" />
</Frame>

The payload is the same whether you use [n8n](/guides/notifyer-system/n8n-overview), [Make](/guides/notifyer-system/make-overview), [Zapier](/guides/notifyer-system/zapier-overview), or a [custom webhook](/guides/notifyer-system/api/incoming-message). [Watch the walkthrough on YouTube](https://www.youtube.com/watch?v=UfW-KwS4gBI).

### Direction, sending system, and team member

Use these three fields to tell *what happened* and *who sent it*:

<ResponseField name="incoming_message" type="boolean">
  `true` when a contact sent a message **to** your business. `false` when your business sent a message **to** the contact (outgoing). Filter on this field to run logic only for one direction.
</ResponseField>

<ResponseField name="send_by" type="string">
  Which system or person sent an **outgoing** message:

  | `send_by` value | Meaning |
  | - | - |
  | `WhatsApp App` | Typed by hand in the WhatsApp Business app on a phone |
  | A team member's name (for example `Axel Meta`) | Sent from the Notifyer chat inbox by that logged-in user |
  | An automation or app name (Make, Zapier, n8n, API, bot) | Sent by that integration or bot |

  Empty or omitted on incoming messages.
</ResponseField>

<ResponseField name="was_message_by_human" type="boolean">
  `true` when a person sent the message (WhatsApp Business app or Notifyer chat inbox). `false` when a bot or automation sent it. Combine with `send_by` to see both *whether* a human sent it and *which teammate or system* did.
</ResponseField>

### Example payload: message typed on the phone

This is the JSON Notifyer POSTs when someone types a reply in the WhatsApp Business app. `incoming_message` is `false`, `send_by` is `"WhatsApp App"`, and `was_message_by_human` is `true`.

```json theme={null}
{
  "last_messages": "[{\"type\":\"bot\",\"content\":\"Hello n8n\",\"timestamp\":\"2026-08-15T12:24:47.000Z\",\"content_type\":\"text\"},{\"type\":\"user\",\"content\":\"hi\",\"timestamp\":\"2026-08-12T12:27:42.746Z\",\"content_type\":\"text\"}]",
  "conversation_paragraph": "Bot (12:24:47 PM): Hello n8n ; User (12:27:42 PM): hi",
  "phone_number": 14155552671,
  "recipient_name": "Alex Martinez",
  "user_id": "158c59e1-ea85-4d0b-b70c-65328ba67a8e",
  "last_message_of_user": "hi",
  "last_message_of_bot": "Hello n8n",
  "message_type": "text",
  "user_last_message_time": 1786722580,
  "bot_last_message_time": 1786797014,
  "attachment_url": null,
  "note": "email: alex\nName: Alex",
  "note_automation": "email: alex\nName: Alex",
  "labels": "n8n, webhook-test",
  "incoming_message": false,
  "send_by": "WhatsApp App",
  "was_message_by_human": true
}
```

<Note>
  `last_message_of_bot` is the last message **your business** sent — whether a human typed it in the WhatsApp Business app or the Notifyer inbox, or a bot/automation sent it. `last_messages` is a JSON **string** of the last \~20 messages (parse it before iterating). `phone_number` may arrive as a number rather than a string.
</Note>

When the same person sends from the Notifyer chat inbox instead of the phone app, the payload is identical except:

```json theme={null}
{
  "incoming_message": false,
  "send_by": "Axel Meta",
  "was_message_by_human": true
}
```

### Click-to-WhatsApp ad attribution

When a contact messages you after tapping a **Click-to-WhatsApp** ad (Facebook, Instagram, or WhatsApp Status), Meta includes a `referral` object on that inbound event. Notifyer forwards it in [webhook](/guides/notifyer-system/api/incoming-message#click-to-whatsapp-ads) and trigger data (n8n, Make, Zapier).

Use it to see **which ad, creative, and platform** produced the lead — then label the chat, route it, or send `ctwa_clid` back to Meta for campaign optimization.

<Note>
  `referral` is typically present on the **first inbound message** after the ad click. Later messages in the same conversation usually omit it. Persist `ctwa_clid` and `source_id` as soon as you see them.
</Note>

| Field | What it tells you |
| - | - |
| `source_type` | `"ad"` for an ad, `"post"` for an organic post |
| `source_id` | Ad or post ID — use this to group leads by creative |
| `source_url` | Where they tapped (Instagram permalink, Facebook/ad URL) |
| `headline` / `body` | Ad copy the lead saw |
| `media_type` | `"image"` or `"video"` |
| `image_url` / `video_url` | Creative asset URL |
| `ctwa_clid` | Click ID for Meta Conversions API attribution |

```json theme={null}
{
  "incoming_message": true,
  "last_message_of_user": "Quiero información",
  "referral": {
    "source_type": "ad",
    "source_id": "52540693396957",
    "source_url": "https://www.instagram.com/p/DZiVBz7gAF9/",
    "headline": "Expo Nissan",
    "body": "Aprovechá la EXPONISSAN y llevate tu nuevo Nissan Kicks Play Sense MT.",
    "media_type": "image",
    "image_url": "https://scontent.xx.fbcdn.net/v/t45.1600-4/example.jpg",
    "ctwa_clid": "AfhN-JKvx8HeFTmfB-Tu11zktQRJ-MNdMV1mwvDNxHnpYrGl-jVf3OEFhLva_MP41zYRe5ErUteWFn3v4gkkjzfIEVr9J_u8GAo3-o6DqShykM4Zsl14FcU5MyThsCoQ"
  }
}
```

If your delivery includes the Cloud API envelope instead of a flattened Notifyer payload, the same object lives at `entry[].changes[].value.messages[].referral`. Full field reference and a complete example: [Message webhooks — Click-to-WhatsApp ads](/guides/notifyer-system/api/incoming-message#click-to-whatsapp-ads).

***

### Actions

Actions perform operations in Notifyer System — sending messages, scheduling follow-ups, updating contacts, and checking delivery status.

***

### Send WhatsApp Message

<Info>
  **Type:** Action | **App:** Whatsable | **Connection:** Notifyer API key
</Info>

**Description in Zapier:** *"Send WhatsApp Messages using the official WhatsApp API. You can add labels to a WhatsApp conversation and also write notes about the lead that will appear in Whatsable's chat interface."*

Send a WhatsApp message immediately to any phone number. Supports both **template messages** (to start a new conversation or send proactive outreach) and **non-template messages** (within an active 24-hour conversation window). Labels and notes set here appear directly in your Notifyer console — making this the core send action for all outbound WhatsApp automation.

***

#### Setting up the action

<Steps>
  <Step title="Add an action step">
    1. In your Zap editor, click **+** to add a new step (or click an existing action step)
    2. Search for **Whatsable** in the app search bar and select it
    3. Under **Action Event**, select **Send WhatsApp Message**
    4. Click **Continue**
  </Step>

  <Step title="Connect your Notifyer account">
    Select your connected Notifyer account from the dropdown, or click **Sign in to Whatsable** to add a new one using your Notifyer API key
  </Step>

  <Step title="Configure the message">
    In the **Configure** section, start by choosing your message type from the **Configuration** dropdown:

    <Tabs>
      <Tab title="Send WhatsApp Template (to start conversation)">
        Use this to **initiate a new conversation** with a contact or send a proactive outreach message. Requires a Meta-approved WhatsApp template.

        <ResponseField name="Phone Number" type="text">
          The recipient's phone number in international format — digits only, no `+` or spaces (e.g. `14155550187`). Map this from a previous trigger step or enter it directly
        </ResponseField>

        <ResponseField name="Template Name or ID" type="dropdown">
          Select from your approved templates. The dropdown shows a live preview of each template's body, language, and category
        </ResponseField>

        <ResponseField name="Body 1, Body 2, ... (variables)" type="text">
          If your template contains variables (`{{1}}`, `{{2}}`...), a separate field appears for each one. Map them to dynamic data from previous steps (e.g. `{{contact_name}}` from a form submission)
        </ResponseField>

        <ResponseField name="Media" type="text">
          If your template has a media header (image, video, or document), enter the publicly accessible URL of that file. Only appears if your selected template includes a media header
        </ResponseField>

        <ResponseField name="Visit Website URL" type="text">
          If your template has a dynamic URL button, enter the full URL value including the dynamic portion
        </ResponseField>

        <ResponseField name="Note" type="text">
          AI context about this contact (name, email, preferences, language, budget). This note is stored on the contact in Notifyer and the AI reads it to personalize future replies. It is not sent to the recipient
        </ResponseField>

        <ResponseField name="Label Names or IDs" type="multiselect">
          Labels to apply to this conversation for internal tracking and routing. Labels appear in your Notifyer console and can be used in scheduling conditions
        </ResponseField>
      </Tab>

      <Tab title="Send a non-template message (person must write to you first)">
        Use this to send a message **within an active conversation** — only possible within 24 hours of the contact's last incoming message. Supports multiple message types.

        <ResponseField name="Recipient Phone Number" type="text">
          The recipient's phone number in international format — digits only, no `+` or spaces (e.g. `14155550187`)
        </ResponseField>

        <ResponseField name="Message Type" type="dropdown">
          Choose what type of message to send:

          <AccordionGroup>
            <Accordion title="Text Message">
              <ResponseField name="Message Content" type="text">
                The text content to send to the contact
              </ResponseField>

              <ResponseField name="Enable Link Preview" type="boolean">
                Set to `true` to show a URL preview card when the message contains a link. Default: `false`
              </ResponseField>
            </Accordion>

            <Accordion title="Image Message">
              <ResponseField name="Image URL" type="url">
                Publicly accessible URL of the image file (JPEG, PNG, etc.)
              </ResponseField>

              <ResponseField name="Caption" type="text">
                Optional caption text displayed below the image
              </ResponseField>
            </Accordion>

            <Accordion title="Video Message">
              <ResponseField name="Video URL" type="url">
                Publicly accessible URL of the video file (MP4, etc.)
              </ResponseField>

              <ResponseField name="Caption" type="text">
                Optional caption text displayed below the video
              </ResponseField>
            </Accordion>

            <Accordion title="Document Message">
              <ResponseField name="Document URL" type="url">
                Publicly accessible URL of the document file (PDF, DOCX, etc.)
              </ResponseField>

              <ResponseField name="Caption" type="text">
                Optional caption for the document
              </ResponseField>

              <ResponseField name="Filename" type="text">
                The filename to display to the recipient (e.g. `invoice-2026.pdf`)
              </ResponseField>
            </Accordion>

            <Accordion title="Audio Message">
              <ResponseField name="Audio URL" type="url">
                Publicly accessible URL of the audio file (MP3, OGG, etc.)
              </ResponseField>
            </Accordion>
          </AccordionGroup>
        </ResponseField>

        <ResponseField name="Label Names or IDs" type="multiselect">
          Labels to apply to this conversation. Labels appear in your Notifyer console
        </ResponseField>

        <ResponseField name="Note" type="text">
          AI context note for this contact — set or update the note that the AI reads to personalize future replies
        </ResponseField>
      </Tab>
    </Tabs>
  </Step>

  <Step title="Test the action">
    1. Click **Continue** to proceed to the **Test** section
    2. Click **Test step** — Zapier will attempt to send a real message using the configuration you set
    3. Check your WhatsApp to confirm the message was received
    4. If the test passes, click **Publish** to activate your Zap (or continue adding more steps first)

    <Warning>
      Testing this action sends a real WhatsApp message. Use a personal test number during setup to avoid sending unintended messages to real contacts.
    </Warning>
  </Step>
</Steps>

***

### Schedule a Follow-Up Message

<Info>
  **Type:** Action | **App:** Whatsable | **Connection:** Notifyer API key
</Info>

**Description in Zapier:** *"Schedule a follow-up to get sent later and add conditions so it only gets sent if the lead did not reply to you."*

Schedule a WhatsApp message to be sent at a **future time**, with an optional **reply condition** that automatically cancels the scheduled message if the recipient responds before it is sent. This is one of Notifyer's most powerful features — use it to build no-reply follow-up sequences, re-engagement drips, and smart nurture workflows that stop automatically when a lead engages.

***

#### Setting up the action

<Steps>
  <Step title="Add an action step">
    1. In your Zap editor, click **+** to add a new step
    2. Search for **Whatsable** and select it
    3. Under **Action Event**, select **Schedule a Follow-Up Message**
    4. Click **Continue**
  </Step>

  <Step title="Connect your Notifyer account">
    Select your connected Notifyer account, or add a new one with your Notifyer API key
  </Step>

  <Step title="Choose your message type">
    In the **Configure** section, select either **Send WhatsApp Template** or **Send a non-template message** from the **Configuration** dropdown.

    The message fields are identical to the **Send WhatsApp Message** action above — fill in the phone number, select your template (or message type), map any variables, and optionally set labels and a note.
  </Step>

  <Step title="Set when to send the message">
    <Tabs>
      <Tab title="Relative (Delay from now)">
        Send the message after a set delay from the moment this Zap step runs:

        <ResponseField name="Delay Value" type="select">
          Choose: 1, 2, 3, 4, 5, 10, 15, 20, 30, 60, 90, or 120
        </ResponseField>

        <ResponseField name="Delay Unit" type="select">
          Choose: **Minutes**, **Hours**, or **Days**
        </ResponseField>
      </Tab>

      <Tab title="Specific Date & Time">
        Send the message at an exact date and time:

        <ResponseField name="Date & Time" type="datetime">
          The exact date and time to send the message. Map this from a previous step (e.g. an appointment datetime from a calendar trigger) or enter a fixed value
        </ResponseField>

        <ResponseField name="Timezone" type="select">
          The timezone for the scheduled time — select from the full global timezone list (GMT-11 through GMT+12)
        </ResponseField>
      </Tab>
    </Tabs>
  </Step>

  <Step title="Set a reply condition (recommended)">
    The reply condition tells Notifyer to **automatically cancel the scheduled message** if the recipient replies within the specified timeframe — preventing follow-up messages from reaching contacts who are already engaged in a conversation with you.

    <ResponseField name="Reply Condition" type="select">
      | Condition | The message is cancelled if... |
      | - | - |
      | Recipient did not reply after my last message | The contact replies at any point before the scheduled send time |
      | Recipient never replied to any of my messages | The contact has never replied to any of your messages |
      | Recipient did not reply within 20 minutes | The contact replies within 20 minutes |
      | Recipient did not reply within 45 minutes | The contact replies within 45 minutes |
      | Recipient did not reply within 3 hours | The contact replies within 3 hours |
      | Recipient did not reply within 6 hours | The contact replies within 6 hours |
      | Recipient did not reply within 12 hours | The contact replies within 12 hours |
      | Recipient did not reply within 24 hours | The contact replies within 24 hours |
      | Recipient did not reply within 48 hours | The contact replies within 48 hours |
      | Recipient did not reply within 72 hours | The contact replies within 72 hours |
    </ResponseField>

    <Tip>
      **"Recipient did not reply after my last message"** is the recommended default for most follow-up sequences — it ensures that no follow-up is sent to contacts who are already in an active conversation with you. This protects your WhatsApp account reputation and keeps communication natural.
    </Tip>
  </Step>

  <Step title="Set a label condition (optional)">
    Restrict the scheduled message so it only sends if the contact has — or does not have — a specific label at the time of sending:

    <ResponseField name="Label Condition" type="select">
      **Include** — only send the message if the contact currently has this label\
      **Does Not Include** — only send the message if the contact does NOT have this label
    </ResponseField>

    <ResponseField name="Label" type="select">
      The label to evaluate when the scheduled send time arrives
    </ResponseField>
  </Step>

  <Step title="Test and activate">
    Click **Continue**, then **Test step** to confirm the follow-up is queued in Notifyer. You can view all pending scheduled messages in your Notifyer console under the contact's conversation.
  </Step>
</Steps>

<Note>
  Scheduled messages are visible in your Notifyer console under each contact's conversation. You can manually cancel any scheduled message there at any time.
</Note>

***

### Update a Contact

<Info>
  **Type:** Action | **App:** Whatsable | **Connection:** Notifyer API key
</Info>

**Description in Zapier:** *"Assign conversation to someone in your team, Add information in the notes, add/remove labels. Simply put the phone number and what information you want to change. This appears in the chat interface of our system."*

Update a contact's details in your Notifyer console — set their display name, add or remove conversation labels, or update the AI context note. Use this to keep Notifyer contacts in sync with your CRM, form submissions, or any other external data source.

***

#### Setting up the action

<Steps>
  <Step title="Add an action step">
    1. In your Zap editor, click **+** to add a new step
    2. Search for **Whatsable** and select it
    3. Under **Action Event**, select **Update a Contact**
    4. Click **Continue**
  </Step>

  <Step title="Connect your Notifyer account">
    Select your connected Notifyer account, or add a new one with your Notifyer API key
  </Step>

  <Step title="Fill in the contact fields">
    <ResponseField name="Phone Number" type="text">
      The phone number of the contact to update, in international format — digits only, no `+` or spaces (e.g. `14155550187`). This is used to look up the contact in your Notifyer console. If the contact does not yet exist, a new record will be created
    </ResponseField>

    <ResponseField name="Display Name" type="text">
      Update the display name shown for this contact in the Notifyer chat interface
    </ResponseField>

    <ResponseField name="Add a Note" type="text">
      Set or update the AI context note for this contact. The AI reads this field to personalize its responses and qualify leads more accurately. A well-structured note dramatically improves AI conversation quality.

      **Recommended note format:**

      ```
      email: john@example.com | Name: John Smith
      Looking for: 3BR house, $500k budget, north suburbs
      Pre-approved: Yes | Language: English
      Best time to contact: evenings after 6pm
      ```
    </ResponseField>

    <ResponseField name="Add Label Names or IDs" type="multiselect">
      One or more labels to **add** to this contact. Labels appear in the Notifyer console and can be used in scheduling conditions and routing rules
    </ResponseField>

    <ResponseField name="Remove Label Names or IDs" type="multiselect">
      One or more labels to **remove** from this contact. Select **Remove All** to clear every label from this contact at once
    </ResponseField>
  </Step>

  <Step title="Test the action">
    Click **Continue**, then **Test step** to confirm the contact is updated in your Notifyer console. Open the contact in your Notifyer dashboard to verify the name, labels, and note appear correctly.
  </Step>
</Steps>

<Tip>
  Place **Update a Contact** as the **first action step** in your Zap — before **Send WhatsApp Message** — to populate the AI Note from form or CRM data. This ensures the AI has full context about the lead before the very first message is sent.
</Tip>

***

### Get Delivery Status of a Message

<Info>
  **Type:** Action | **App:** Whatsable | **Connection:** Notifyer API key
</Info>

**Description in Zapier:** *"Check if the message was delivered or not. Use this if you're not sure the number is correct and want to check if it was delivered and want to send a fallback email."*

Check whether a previously sent WhatsApp message was successfully delivered to the recipient. Use this to build fallback automation — if a message was not delivered (for example, because the phone number is incorrect or inactive), automatically trigger an alternative action such as sending a fallback email.

***

#### Setting up the action

<Steps>
  <Step title="Add an action step">
    1. In your Zap editor, click **+** to add a new step **after** a Send WhatsApp Message or Schedule a Follow-Up Message action
    2. Search for **Whatsable** and select it
    3. Under **Action Event**, select **Get Delivery Status of a Message**
    4. Click **Continue**
  </Step>

  <Step title="Connect your Notifyer account">
    Select your connected Notifyer account, or add a new one with your Notifyer API key
  </Step>

  <Step title="Enter the Message ID">
    <ResponseField name="Message ID" type="text">
      The ID of the message to check. This is returned in the output data of the **Send WhatsApp Message** or **Schedule a Follow-Up Message** action that ran earlier in the same Zap. Map it from that step's output using Zapier's data mapper
    </ResponseField>

    Click **Continue** when done.
  </Step>

  <Step title="Test and use the result">
    Click **Test step**. Zapier will call Notifyer and return the delivery status of that message.

    Use the returned status field in a **Filter** step immediately after this action to create two paths:

    * **Delivered** → continue your main workflow
    * **Not Delivered** → send a fallback email via Gmail, Outlook, or another email app
  </Step>
</Steps>

<Tip>
  Add a Zapier **Filter** or **Paths** step after **Get Delivery Status** to branch your Zap: route successfully delivered messages down one path and undelivered messages down another where you send a fallback email or alert.
</Tip>

***

## Building a complete Zap: step-by-step example

Here is a practical end-to-end example: **New lead from a form → AI context set → Template message sent → Conditional follow-up scheduled**

<Steps>
  <Step title="Trigger: New form submission">
    Start with a **Google Forms**, **Typeform**, or **Jotform** trigger that fires instantly when someone fills in your lead capture form
  </Step>

  <Step title="Action: Update a Contact">
    Add **Whatsable — Update a Contact**. Map form fields into the Note field:

    ```
    email: {{email}} | Name: {{name}} | Budget: {{budget}} | Language: {{language}}
    ```

    Add relevant labels: `New Lead`, `Form Submission`

    This gives the AI complete context before any conversation starts.
  </Step>

  <Step title="Action: Send WhatsApp Message (Template)">
    Add **Whatsable — Send WhatsApp Message** set to the template configuration. Select your approved welcome template, then map the recipient's phone number and any template variables from the form data
  </Step>

  <Step title="Action: Schedule a Follow-Up Message">
    Add **Whatsable — Schedule a Follow-Up Message**. Configure:

    * Message: a follow-up template (e.g. `Hi {{1}}, just checking in...`)
    * Schedule: **24 Hours** (Relative delay)
    * Reply condition: **Recipient did not reply after my last message**

    This follow-up cancels automatically if the lead responds to your first message.
  </Step>

  <Step title="Test and activate">
    1. Click **Test** on each step to verify all steps show a success result
    2. Click **Publish** to save your Zap
    3. Toggle the **On/Off** switch to **On** to activate it
  </Step>
</Steps>

***

## Example use cases

<CardGroup>
  <Card title="AI chatbot lead qualification" icon="robot">
    Trigger on incoming messages, pass `conversation_paragraph` and `note` to OpenAI, then send the AI's reply back via Send WhatsApp Message
  </Card>

  <Card title="Smart follow-up sequences" icon="calendar-clock">
    Schedule a series of follow-ups with reply conditions — they cancel automatically when the lead engages so you never over-message
  </Card>

  <Card title="CRM-to-WhatsApp sync" icon="database">
    When a deal stage changes in HubSpot or Pipedrive, use Update a Contact to update the AI note, then send a relevant WhatsApp template
  </Card>

  <Card title="Form-to-WhatsApp onboarding" icon="file-lines">
    When a form is submitted, instantly set AI context via Update a Contact, then send a personalized onboarding template message
  </Card>

  <Card title="Delivery fallback" icon="envelope">
    Use Get Delivery Status after sending a message — if undelivered, route to a fallback email via Gmail or Outlook
  </Card>

  <Card title="Real-time CRM logging" icon="list">
    Trigger on every incoming or outgoing message and log the conversation data to a Google Sheet, Airtable, or your CRM in real time
  </Card>
</CardGroup>

***

## Best practices

<AccordionGroup>
  <Accordion title="Set the AI Note before sending" icon="robot">
    Always use **Update a Contact** as the first action in new-lead Zaps — before **Send WhatsApp Message**. Setting the `note` field with structured lead data (name, email, preferences, language, budget) dramatically improves AI conversation quality and lead qualification accuracy.
  </Accordion>

  <Accordion title="Always use reply conditions on follow-ups" icon="shield-check">
    Set a reply condition on every **Schedule a Follow-Up Message** action. "Recipient did not reply after my last message" is the safest choice — it ensures no follow-up is sent to contacts who are already in an active conversation. This also protects your WhatsApp account reputation.
  </Accordion>

  <Accordion title="Use labels on every send and update" icon="tag">
    Both **Send WhatsApp Message** and **Update a Contact** let you attach labels to conversations. Use labels to tag contacts (e.g. `Hot Lead`, `Form Submission`, `Appointment Set`) — they appear in your Notifyer console and can be used in label conditions for scheduling.
  </Accordion>

  <Accordion title="Use conversation_paragraph for AI prompts" icon="paragraph">
    When building AI chatbot Zaps, map the `conversation_paragraph` trigger field to your OpenAI or Claude prompt. It is a pre-formatted, readable version of the full conversation — much simpler to include in a prompt than parsing the raw `last_messages` JSON array.
  </Accordion>

  <Accordion title="Filter by incoming_message for one-direction flows" icon="filter">
    The trigger fires on both incoming and outgoing messages by default. Add a Zapier **Filter** step immediately after the trigger and filter by `incoming_message = true` if you only want your Zap to react when a contact writes to you, or `incoming_message = false` to react only when your business sends a message (including replies typed in the WhatsApp Business app). Use `send_by` to distinguish `"WhatsApp App"`, a teammate name, and automations.
  </Accordion>

  <Accordion title="Capture Click-to-WhatsApp referral on the first message" icon="bullhorn">
    When `referral` is present, store `source_id`, `source_url`, `headline`, and `ctwa_clid` on the contact immediately. Later messages in the same chat usually omit `referral`. Use `source_url` to see Instagram vs Facebook, and `source_id` to compare creatives.
  </Accordion>

  <Accordion title="Phone number format" icon="phone">
    Always provide phone numbers in full international format — digits only, no `+`, spaces, or dashes (e.g. `14155550187` for US, `447911123456` for UK, `966501234567` for Saudi Arabia).
  </Accordion>
</AccordionGroup>

***

## Troubleshooting

<AccordionGroup>
  <Accordion title="Trigger not firing?" icon="circle-exclamation">
    <Steps>
      <Step title="Check your Zap is turned on">
        The trigger only fires when the Zap is toggled **On**. Go to your Zap's overview page and confirm the On/Off switch is set to **On**
      </Step>

      <Step title="Verify your connected account">
        Open the trigger step in your Zap editor, go to the **Account** section, and confirm your Whatsable connected account shows no errors. If it does, disconnect and reconnect with your Notifyer API key
      </Step>

      <Step title="Send a test message">
        Zapier's **Test trigger** button requires at least one recent event in your Notifyer console. Send a WhatsApp message to your connected number — or type a reply in the WhatsApp Business app — and then re-test. You do not need to delete the WhatsApp Business app.
      </Step>

      <Step title="Check your Notifyer console">
        If messages appear in your Notifyer console but the trigger still does not fire, contact support — there may be a webhook configuration issue
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Messages not sending?" icon="message-xmark">
    <Steps>
      <Step title="Check the connected account">
        Verify your Notifyer API key is valid and the correct connected account is selected in the action step
      </Step>

      <Step title="Check phone number format">
        Phone number must be digits only in full international format, no `+` or spaces (e.g. `14155550187`)
      </Step>

      <Step title="Template not approved?">
        Ensure the selected template has **Approved** status in your Notifyer dashboard. Pending or rejected templates will cause an error
      </Step>

      <Step title="24-hour window for non-template messages">
        Non-template messages can only be sent within 24 hours of the contact's last incoming message. Outside this window you must use an approved template
      </Step>

      <Step title="Check subscription credits">
        Verify your Notifyer subscription is active and has sufficient message credits
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Template variables not populating?" icon="brackets-curly">
    <Steps>
      <Step title="Fill all required variable fields">
        All body variable fields (Body 1, Body 2, etc.) are required — confirm none are empty or mapped to fields that return empty values
      </Step>

      <Step title="Check the template preview">
        The template dropdown in the action configuration shows a preview of the body text and example values — use this as a reference to understand what each variable slot expects
      </Step>

      <Step title="Media URL must be public">
        If your template has a media header, the URL must be publicly accessible. Test it by opening it in an incognito browser window
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Scheduled message was not sent?" icon="clock">
    <Steps>
      <Step title="Reply condition may have cancelled it">
        If you set a reply condition and the contact replied before the scheduled send time, the message was intentionally cancelled. Check the contact's conversation in your Notifyer console
      </Step>

      <Step title="Verify the delay settings">
        Confirm the delay value and unit are correct (e.g. `24` + `Hours`, not `24` + `Minutes`)
      </Step>

      <Step title="Check your Zap run history">
        In Zapier, go to **Zap History** and find the run where the Schedule a Follow-Up Message step executed. Confirm the step shows a success status at the time the trigger fired
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Update a Contact changes not appearing in Notifyer?" icon="user-pen">
    <Steps>
      <Step title="Verify the phone number">
        The phone number must exactly match the contact's number in Notifyer (same international format). If no contact with that number exists, Notifyer will create a new record
      </Step>

      <Step title="Confirm you are using the correct connection">
        The **Update a Contact** action requires the Notifyer connection (the one authenticated with your Notifyer API key). Confirm the correct connected account is selected in the action step
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="Get Delivery Status returning no result?" icon="circle-question">
    <Steps>
      <Step title="Map the correct Message ID">
        The Message ID field must be mapped from the output of a **Send WhatsApp Message** or **Schedule a Follow-Up Message** step in the same Zap. Make sure you are mapping the `message_id` field from the correct preceding action step
      </Step>

      <Step title="Allow time for delivery">
        Delivery status may take a few seconds to update after a message is sent. If checking status immediately after sending, consider adding a short delay using Zapier's **Delay** action before the Get Delivery Status step
      </Step>
    </Steps>
  </Accordion>
</AccordionGroup>

***

## Need help?

<CardGroup>
  <Card title="Email support" icon="envelope" href="mailto:team@whatsable.app">
    Contact [team@whatsable.app](mailto:team@whatsable.app)
  </Card>

  <Card title="Schedule a demo" icon="calendar" href="https://tidycal.com/axelmeta/notifyer-systems-demo">
    Book a personalized walkthrough
  </Card>

  <Card title="Live chat" icon="message-dots">
    Click the green chat button in the bottom right corner of the Notifyer System dashboard
  </Card>
</CardGroup>


# What are Whatsable and Meta messaging rate limits?
Source: https://docs.whatsable.app/guides/rate-limits

Meta WhatsApp MPS (80 default; 20 on Coexistence), messaging caps outside the 24h window, error 130429, and that Whatsable’s API RPM is still unpublished.

WhatsApp throughput and messaging caps are set by **Meta**, not by a Whatsable plan slider. This page covers Meta **messages-per-second (MPS)** limits, the lower Coexistence MPS cap, Meta **messaging limits** outside the 24-hour customer-service window, and what Whatsable does **not** publish as a numeric API rate (RPM).

If you need how to connect a number, start with [Connect WhatsApp (Embedded Signup + Coexistence)](/guides/whatsable/connect-whatsapp-coexistence). For plan gates and unique-contact billing, see [plans Bulk Message / Pro / Agency](/guides/notifyer-system/plans-bulk-message-pro-agency).

***

## Two different Meta limits

Do not mix these up:

| Limit type | What it controls | Who enforces it |
| - | - | - |
| **Throughput (MPS)** | How fast a business phone number can send/receive messages on Cloud API | Meta (per phone number) |
| **Messaging limits** | How many **unique** WhatsApp users you can message **outside** a customer-service window in a rolling 24 hours | Meta (portfolio / business capability) |

Whatsable sits on Meta Cloud API. Hitting either limit shows up as Meta errors or undelivered business-initiated traffic — not as a Whatsable “upgrade your RPM” control in the console.

***

## Meta throughput (messages per second)

Cite Meta’s [Throughput](https://developers.facebook.com/documentation/business-messaging/whatsapp/throughput) documentation for the live numbers. As of Meta’s published Throughput page (updated **2026-06-17**):

| Phone-number situation | Meta MPS (throughput) |
| - | - |
| Default Cloud API number | Up to **80** messages per second |
| Automatic upgrade (eligibility met) | Up to **1,000** messages per second |
| **Coexistence** (WhatsApp Business app + Cloud API on the same number) | Fixed **20** messages per second |

Meta notes that throughput counts **inbound and outbound** traffic and all message types. Numbers remain subject to WhatsApp Business Account rate limits and template messaging limits even after a throughput upgrade.

**Exceeding throughput:** Meta returns Cloud API error **`130429`** (“Cloud API message throughput has been reached”) until you are back under the allowed level. Match on `code` and `error_data.details`, not on titles — see [WhatsApp Cloud API error 130429](/whatsapp-error-130429).

**Higher throughput:** Meta can auto-upgrade a number to 1,000 MPS when the portfolio has an unlimited messaging limit, the number messages enough unique users outside the service window in a rolling day, and quality is Medium (yellow) or higher. Eligibility and exact checks live on Meta’s Throughput page — Whatsable does not sell or flip that upgrade.

***

## Coexistence throughput (20 MPS)

Most Whatsable customers keep the **WhatsApp Business app** on the phone while using Cloud API (**Coexistence**). Meta fixes Coexistence numbers at **20 MPS** so the app and API stay compatible. That cap is a **Meta-side** constraint.

Whatsable notes that match this page:

* Coexistence throughput is **Meta’s**, not a Whatsable product limit you can raise in Settings.
* Do **not** uninstall the WhatsApp Business app after connect — that breaks Coexistence.
* Unofficial (non-Meta) API tools on that number stop once Coexistence is on.

Operator connect guide: [Connect WhatsApp Business to Whatsable](/guides/whatsable/connect-whatsapp-coexistence). Outbound when humans type in the Business app: [Outbound WhatsApp Business app](/guides/notifyer-system/api/outbound-whatsapp-app).

***

## Meta messaging limits (unique recipients / day)

Separate from MPS: Meta caps how many **unique** customer numbers a business can message **outside** the customer-service window in a moving 24-hour period. Inside the window (the customer messaged you recently), free-form replies are not gated by that unique-recipient messaging-limit ladder.

Exact tier values and scaling rules change on Meta’s side. Treat [Meta Messaging Limits](https://developers.facebook.com/docs/whatsapp/messaging-limits/) and WhatsApp Manager as the live source — do not hard-code a Whatsable “daily RPM.”

Operator notes (not a substitute for Meta’s page):

* Outside the 24-hour window, only **approved templates** start business-initiated conversations.
* Unverified Meta Business Portfolios start with a low daily unique-recipient cap; verified portfolios scale through Meta’s messaging-limit tiers up to unlimited.
* Customer replies that open or refresh the service window are not “using up” that business-initiated unique-recipient ladder the same way.

This rate-limits page only separates **messaging limits** from **MPS** so you do not mix them into one invented number.

***

## Whatsable API rate limits (RPM)

**Unpublished / unknown.** Whatsable does **not** currently publish a numeric requests-per-minute (RPM) figure for its own HTTP APIs in customer docs.

* Do **not** invent a Whatsable RPM, “generous rate limit,” or plan-based API quota.
* Use the **Meta MPS**, **Coexistence**, and **messaging limits** sections on this page.
* If a send fails with Meta throughput details, treat it as Meta `130429` / Throughput — not as a missing Whatsable RPM table.

***

## Pair rate and burst behavior (Meta)

Meta also applies **pair** rate limits when you send too many messages to the **same** WhatsApp user too quickly (separate from phone-number MPS). Meta documents this on Cloud API overview / error materials (for example throttling around error **`131056`**). Campaigns that spray many different recipients are what MPS is sized for; hammering one user is a different Meta pair limit.

Whatsable does not override Meta pair limits.

***

## Operator checklist when sends slow or fail

1. **Read the error `code` and `details`.** Throughput → [130429](/whatsapp-error-130429). Do not match deprecated titles alone.
2. **Check Coexistence.** If the number still uses the WhatsApp Business app, Meta MPS is **20**, not the default 80 / 1000 ladder.
3. **Separate MPS from messaging limits.** A green throughput number can still fail business-initiated templates if Meta messaging limits / quality / cold outreach rules apply.
4. **Warm gradually on cold lists** (especially US). Meta may withhold delivery for healthy-ecosystem reasons — related codes live under Whatsable’s Meta error pages (for example [131049](/whatsapp-error-131049)).
5. **Do not uninstall** the Business app to “raise” throughput. That breaks Coexistence; Meta’s Coexistence MPS cap remains the documented path for dual-app numbers.

***

## What this page does not claim

* No invented **Whatsable numeric RPM** or plan-based API quota.
* No marketing comparisons to other BSPs.
* No typing-indicator / “dots” product claims.
* No native drip builder (sequences stay in Make / Zapier / n8n).
* No rate-dashboard UI that is not present in your console.
* Exact Meta messaging-limit tier integers are **not** copied here as everlasting Whatsable facts — use Meta’s Messaging Limits page and WhatsApp Manager.

***

## FAQ

### Does Whatsable raise Meta’s 20 MPS Coexistence limit?

No. Coexistence MPS is fixed by Meta for app + API numbers. Whatsable does not control or raise it.

### Where do plan unique-contact limits fit?

Those are **Whatsable billing** (unique contacts / overage), not Meta MPS. See [plans Bulk Message / Pro / Agency](/guides/notifyer-system/plans-bulk-message-pro-agency); money stays on [pricing](https://whatsable.app/pricing).

***

<CardGroup>
  <Card title="Connect WhatsApp (Coexistence)" icon="link" href="/guides/whatsable/connect-whatsapp-coexistence">
    Embedded Signup, keep the Business app, Meta-side throughput honesty.
  </Card>

  <Card title="Error 130429 (throughput)" icon="triangle-exclamation" href="/whatsapp-error-130429">
    Match code + details when Cloud API MPS is exceeded.
  </Card>

  <Card title="Outbound Business app" icon="mobile" href="/guides/notifyer-system/api/outbound-whatsapp-app">
    Human replies typed in the WhatsApp Business app on Coexistence.
  </Card>

  <Card title="Meta Throughput (external)" icon="book" href="https://developers.facebook.com/documentation/business-messaging/whatsapp/throughput">
    Meta’s live MPS, Coexistence 20 MPS, and upgrade eligibility.
  </Card>
</CardGroup>


# Webhooks
Source: https://docs.whatsable.app/guides/webhooks

Receive real-time notifications for message status and incoming messages via webhooks.

# Webhooks

Webhooks allow you to receive real-time notifications about message status and incoming messages.

## Overview

Webhooks provide a way for our system to send data to your application in real-time whenever:

* A message status changes
* A recipient replies to your message
* A new message is received

## Setting Up Webhooks

1. Go to your Whatsable dashboard
2. Navigate to Developer Settings
3. Click "Add Webhook"
4. Enter your webhook URL
5. Select the events you want to receive

## Webhook Events

### Message Status Events

```json theme={null}
{
  "event": "message_status",
  "data": {
    "message_id": "wamid.123456789",
    "status": "delivered",
    "timestamp": "2024-03-23T21:41:44.477Z"
  }
}
```

### Incoming Message Events

```json theme={null}
{
  "event": "incoming_message",
  "data": {
    "last_messages": "[{\"type\":\"user\",\"content\":\"Hello!\",\"timestamp\":\"2024-03-23T21:41:44.477Z\",\"content_type\":\"text\"}]",
    "conversation_paragraph": "User (9:41:44 PM): Hello!",
    "phone_number": "8801734363287",
    "recipient_name": "John Doe",
    "user_id": "6fb11ff2-d9b2-4560-8437-0fe58ec9f4a6",
    "last_message_of_user": "Hello!",
    "last_message_of_bot": "Hi there!",
    "message_type": "text",
    "user_timestamp": 1234567890,
    "bot_timestamp": 1234567890,
    "attachment_url": "https://api.insightssystem.com/vault/attachment.jpg"
  }
}
```

## Webhook Security

1. **HTTPS Required**: All webhook endpoints must be accessible via HTTPS
2. **Authentication**: Verify webhook signatures
3. **IP Whitelisting**: Configure allowed IP addresses
4. **Rate Limiting**: Handle multiple events efficiently

## Best Practices

1. **Idempotency**: Handle duplicate events gracefully
2. **Error Handling**: Return appropriate HTTP status codes
3. **Logging**: Log all incoming webhook events
4. **Monitoring**: Set up alerts for webhook failures
5. **Testing**: Use the webhook testing tool in dashboard

## Example Webhook Handler

```javascript theme={null}
const express = require('express');
const app = express();

app.post('/webhook', express.json(), (req, res) => {
  const { event, data } = req.body;

  switch (event) {
    case 'message_status':
      handleMessageStatus(data);
      break;
    case 'incoming_message':
      handleIncomingMessage(data);
      break;
    default:
      console.log('Unknown event type:', event);
  }

  res.status(200).send('OK');
});

function handleMessageStatus(data) {
  console.log('Message status update:', data);
  // Process message status
}

function handleIncomingMessage(data) {
  console.log('Incoming message:', data);
  // Process incoming message
}

app.listen(3000, () => {
  console.log('Webhook server running on port 3000');
});
```


# Whatsable API
Source: https://docs.whatsable.app/guides/whatsable/api-documentation

Send programmatic WhatsApp messages with the Whatsable API

# Whatsable API

> Send programmatic WhatsApp messages with ease

<Frame>
  <img alt="Whatsable API Hero Image" />

  <img alt="Whatsable API Hero Image" />
</Frame>

## Overview

Whatsable API enables developers to programmatically send WhatsApp messages with rich media support. Our RESTful API delivers enterprise-grade reliability while maintaining a simple integration process. Whether you're building a customer support platform, marketing automation system, or notification service, Whatsable API gives you the tools to engage your users on WhatsApp.

<CardGroup>
  <Card title="Quick Start" icon="bolt" href="#getting-started">
    Send your first WhatsApp message in under 5 minutes
  </Card>

  <Card title="API Reference" icon="code" href="#api-reference">
    Complete API endpoints and parameters documentation
  </Card>

  <Card title="Media Support" icon="image" href="#supported-media-types">
    Send images, videos, documents, and more
  </Card>

  <Card title="Templates" icon="layer-group" href="#template-based-messaging">
    Use templates for structured messages
  </Card>
</CardGroup>

## Key Features

<AccordionGroup>
  <Accordion title="Rich Media Messaging" icon="photo-film">
    Send WhatsApp messages with text, images, videos, documents, and audio files.
  </Accordion>

  <Accordion title="Template-Based Messaging" icon="layer-group">
    Use pre-defined templates for structured messages, enabling you to send consistent communications.
  </Accordion>

  <Accordion title="No-Code Integration" icon="puzzle-piece">
    Seamlessly integrate with platforms like Zapier and Make.com without writing code.
  </Accordion>

  <Accordion title="Enterprise Scalability" icon="chart-line">
    Send messages to thousands of recipients with high deliverability and reliability.
  </Accordion>
</AccordionGroup>

## Getting Started

<Steps>
  <Step title="Create a Whatsable Account">
    Sign up for a [Whatsable account](https://dashboard.whatsable.app/register) and activate your subscription or start a free trial.

    <Note>
      You'll need a WhatsApp-enabled phone number to send messages from your account.
    </Note>
  </Step>

  <Step title="Obtain Your API Key">
    Navigate to the API section in your Whatsable dashboard and generate an API key.

    <Warning>
      Keep your API key secure and never share it publicly. It grants full access to send messages from your account.
    </Warning>
  </Step>

  <Step title="Send Your First Message">
    Use the examples below to send your first WhatsApp message programmatically.
  </Step>
</Steps>

## API Reference

### Base URL

<CodeGroup>
  ```bash Base URL theme={null}
  https://dashboard.whatsable.app/api/whatsapp/messages/v2.0.0
  ```

  ```bash Legacy URL (v1) theme={null}
  https://dashboard.whatsable.app/api/whatsapp/messages
  ```
</CodeGroup>

### Authentication

All API requests require authentication using your API key in the request header:

<ParamField type="string">
  Your Whatsable API key
</ParamField>

<CodeGroup>
  ```bash Example theme={null}
  curl -X POST https://dashboard.whatsable.app/api/whatsapp/messages/v2.0.0/send \
  -H 'Authorization: YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "to": "+1234567890",
    "text": "Hello from WhatsAble!"
  }'
  ```
</CodeGroup>

### Send Message Endpoint

<ParamField type="string">
  Endpoint to send WhatsApp messages
</ParamField>

#### Request Parameters

<ResponseField name="Body Parameters" type="Object">
  <Expandable title="properties">
    <ResponseField name="to" type="string">
      The recipient's phone number in E.164 format (e.g., +1234567890)
    </ResponseField>

    <ResponseField name="text" type="string">
      The message content you want to send
    </ResponseField>

    <ResponseField name="attachment" type="string">
      URL or base64-encoded file for attachments (images, videos, PDFs)
    </ResponseField>

    <ResponseField name="filename" type="string">
      Name of the file when sending a document attachment
    </ResponseField>
  </Expandable>
</ResponseField>

#### Response

<ResponseField name="Success Response" type="Object">
  <Expandable title="properties">
    <ResponseField name="success" type="boolean">
      Indicates if the message was sent successfully (true)
    </ResponseField>

    <ResponseField name="message" type="string">
      A human-readable message describing the result
    </ResponseField>

    <ResponseField name="details" type="object">
      <Expandable title="properties">
        <ResponseField name="messages" type="array">
          <Expandable title="properties">
            <ResponseField name="id" type="string">
              Unique identifier for the message (e.g., wamid.XXXXXX)
            </ResponseField>

            <ResponseField name="message_status" type="string">
              Status of the message (e.g., "accepted")
            </ResponseField>
          </Expandable>
        </ResponseField>
      </Expandable>
    </ResponseField>
  </Expandable>
</ResponseField>

<RequestExample>
  ```bash cURL theme={null}
  curl -X POST https://dashboard.whatsable.app/api/whatsapp/messages/v2.0.0/send \
  -H 'Authorization: YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "to": "+1234567890",
    "text": "Hello, this is a test message from WhatsAble!",
    "attachment": "https://example.com/image.jpg",
    "filename": "image.jpg"
  }'
  ```
</RequestExample>

<ResponseExample>
  ```json Success Response theme={null}
  {
    "success": true,
    "message": "Message sent successfully to +1234567890",
    "details": {
      "messages": [
        {
          "id": "wamid.XXXXXX",
          "message_status": "accepted"
        }
      ]
    }
  }
  ```
</ResponseExample>

### Error Codes

<AccordionGroup>
  <Accordion title="400 Bad Request">
    ```json theme={null}
    {
      "success": false,
      "message": "Invalid phone number format",
      "details": "Phone number must be in E.164 format."
    }
    ```

    <Tip>
      Ensure phone numbers are in E.164 format (e.g., +1234567890) with country code.
    </Tip>
  </Accordion>

  <Accordion title="401 Unauthorized">
    ```json theme={null}
    {
      "success": false,
      "message": "API key is required"
    }
    ```

    <Warning>
      Make sure you're including the API key in the Authorization header.
    </Warning>
  </Accordion>

  <Accordion title="403 Forbidden">
    ```json theme={null}
    {
      "success": false,
      "message": "Invalid API Key"
    }
    ```

    <Warning>
      Verify your API key is correct and active in your Whatsable dashboard.
    </Warning>
  </Accordion>

  <Accordion title="404 Not Found">
    ```json theme={null}
    {
      "success": false,
      "message": "The number +1234567890 is not registered."
    }
    ```

    <Info>
      The recipient's number must be registered with WhatsApp to receive messages.
    </Info>
  </Accordion>
</AccordionGroup>

## Code Examples

<CodeGroup>
  ```javascript JavaScript (Fetch) theme={null}
  const sendWhatsAppMessage = async () => {
    const apiKey = 'YOUR_API_KEY';
    const endpoint = 'https://dashboard.whatsable.app/api/whatsapp/messages/v2.0.0/send';
    
    const payload = {
      to: '+1234567890',
      text: 'Hello, this is a test message from WhatsAble!',
      attachment: 'https://example.com/image.jpg',
      filename: 'image.jpg'
    };
    
    try {
      const response = await fetch(endpoint, {
        method: 'POST',
        headers: {
          'Authorization': apiKey,
          'Content-Type': 'application/json'
        },
        body: JSON.stringify(payload)
      });
      
      const data = await response.json();
      console.log('Message sent:', data);
      return data;
    } catch (error) {
      console.error('Error sending message:', error);
      throw error;
    }
  };

  sendWhatsAppMessage();
  ```

  ```python Python theme={null}
  import requests
  import json

  def send_whatsapp_message():
      api_key = 'YOUR_API_KEY'
      endpoint = 'https://dashboard.whatsable.app/api/whatsapp/messages/v2.0.0/send'
      
      payload = {
          'to': '+1234567890',
          'text': 'Hello, this is a test message from WhatsAble!',
          'attachment': 'https://example.com/image.jpg',
          'filename': 'image.jpg'
      }
      
      headers = {
          'Authorization': api_key,
          'Content-Type': 'application/json'
      }
      
      try:
          response = requests.post(endpoint, headers=headers, data=json.dumps(payload))
          data = response.json()
          print('Message sent:', data)
          return data
      except Exception as e:
          print('Error sending message:', str(e))
          raise e

  send_whatsapp_message()
  ```

  ```php PHP theme={null}
  <?php

  function sendWhatsAppMessage() {
      $apiKey = 'YOUR_API_KEY';
      $endpoint = 'https://dashboard.whatsable.app/api/whatsapp/messages/v2.0.0/send';
      
      $payload = [
          'to' => '+1234567890',
          'text' => 'Hello, this is a test message from WhatsAble!',
          'attachment' => 'https://example.com/image.jpg',
          'filename' => 'image.jpg'
      ];
      
      $headers = [
          'Authorization: ' . $apiKey,
          'Content-Type: application/json'
      ];
      
      $ch = curl_init($endpoint);
      curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
      curl_setopt($ch, CURLOPT_POST, true);
      curl_setopt($ch, CURLOPT_POSTFIELDS, json_encode($payload));
      curl_setopt($ch, CURLOPT_HTTPHEADER, $headers);
      
      $response = curl_exec($ch);
      $error = curl_error($ch);
      curl_close($ch);
      
      if ($error) {
          echo 'Error sending message: ' . $error;
          return false;
      }
      
      $data = json_decode($response, true);
      echo 'Message sent: ' . print_r($data, true);
      return $data;
  }

  sendWhatsAppMessage();
  ```
</CodeGroup>

## Supported Media Types

Whatsable API supports a wide range of media types for sending rich messages via WhatsApp.

<Tabs>
  <Tab title="Images">
    <ResponseField name="Supported Formats" type="Object">
      <Expandable title="formats">
        <ResponseField name="JPEG" type="Image">
          <Expandable title="specifications">
            <ResponseField name="Extension" type="string">
              .jpeg, .jpg
            </ResponseField>

            <ResponseField name="MIME Type" type="string">
              image/jpeg
            </ResponseField>

            <ResponseField name="Max Size" type="string">
              5MB
            </ResponseField>

            <ResponseField name="Requirements" type="string">
              8-bit, RGB or RGBA
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="PNG" type="Image">
          <Expandable title="specifications">
            <ResponseField name="Extension" type="string">
              .png
            </ResponseField>

            <ResponseField name="MIME Type" type="string">
              image/png
            </ResponseField>

            <ResponseField name="Max Size" type="string">
              5MB
            </ResponseField>

            <ResponseField name="Requirements" type="string">
              8-bit, RGB or RGBA
            </ResponseField>
          </Expandable>
        </ResponseField>
      </Expandable>
    </ResponseField>

    <CodeGroup>
      ```javascript Send Image Example theme={null}
      const payload = {
        to: '+1234567890',
        text: 'Check out this image!',
        attachment: 'https://example.com/image.jpg',
        filename: 'image.jpg'
      };
      ```
    </CodeGroup>
  </Tab>

  <Tab title="Videos">
    <ResponseField name="Supported Formats" type="Object">
      <Expandable title="formats">
        <ResponseField name="MP4" type="Video">
          <Expandable title="specifications">
            <ResponseField name="Extension" type="string">
              .mp4
            </ResponseField>

            <ResponseField name="MIME Type" type="string">
              video/mp4
            </ResponseField>

            <ResponseField name="Max Size" type="string">
              16MB
            </ResponseField>

            <ResponseField name="Codec" type="string">
              H.264 video, AAC audio
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="3GPP" type="Video">
          <Expandable title="specifications">
            <ResponseField name="Extension" type="string">
              .3gp
            </ResponseField>

            <ResponseField name="MIME Type" type="string">
              video/3gpp
            </ResponseField>

            <ResponseField name="Max Size" type="string">
              16MB
            </ResponseField>

            <ResponseField name="Codec" type="string">
              H.264 video, AAC audio
            </ResponseField>
          </Expandable>
        </ResponseField>
      </Expandable>
    </ResponseField>
  </Tab>

  <Tab title="Documents">
    <ResponseField name="Supported Formats" type="Object">
      <Expandable title="formats">
        <ResponseField name="PDF" type="Document">
          <Expandable title="specifications">
            <ResponseField name="Extension" type="string">
              .pdf
            </ResponseField>

            <ResponseField name="MIME Type" type="string">
              application/pdf
            </ResponseField>

            <ResponseField name="Max Size" type="string">
              100MB
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="Microsoft Word" type="Document">
          <Expandable title="specifications">
            <ResponseField name="Extension" type="string">
              .doc, .docx
            </ResponseField>

            <ResponseField name="MIME Type" type="string">
              application/msword, application/vnd.openxmlformats-officedocument.wordprocessingml.document
            </ResponseField>

            <ResponseField name="Max Size" type="string">
              100MB
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="Microsoft Excel" type="Document">
          <Expandable title="specifications">
            <ResponseField name="Extension" type="string">
              .xls, .xlsx
            </ResponseField>

            <ResponseField name="MIME Type" type="string">
              application/vnd.ms-excel, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
            </ResponseField>

            <ResponseField name="Max Size" type="string">
              100MB
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="Microsoft PowerPoint" type="Document">
          <Expandable title="specifications">
            <ResponseField name="Extension" type="string">
              .ppt, .pptx
            </ResponseField>

            <ResponseField name="MIME Type" type="string">
              application/vnd.ms-powerpoint, application/vnd.openxmlformats-officedocument.presentationml.presentation
            </ResponseField>

            <ResponseField name="Max Size" type="string">
              100MB
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="Text" type="Document">
          <Expandable title="specifications">
            <ResponseField name="Extension" type="string">
              .txt
            </ResponseField>

            <ResponseField name="MIME Type" type="string">
              text/plain
            </ResponseField>

            <ResponseField name="Max Size" type="string">
              100MB
            </ResponseField>
          </Expandable>
        </ResponseField>
      </Expandable>
    </ResponseField>
  </Tab>

  <Tab title="Audio">
    <ResponseField name="Supported Formats" type="Object">
      <Expandable title="formats">
        <ResponseField name="MP3" type="Audio">
          <Expandable title="specifications">
            <ResponseField name="Extension" type="string">
              .mp3
            </ResponseField>

            <ResponseField name="MIME Type" type="string">
              audio/mpeg
            </ResponseField>

            <ResponseField name="Max Size" type="string">
              16MB
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="AAC" type="Audio">
          <Expandable title="specifications">
            <ResponseField name="Extension" type="string">
              .aac
            </ResponseField>

            <ResponseField name="MIME Type" type="string">
              audio/aac
            </ResponseField>

            <ResponseField name="Max Size" type="string">
              16MB
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="OGG (OPUS)" type="Audio">
          <Expandable title="specifications">
            <ResponseField name="Extension" type="string">
              .ogg
            </ResponseField>

            <ResponseField name="MIME Type" type="string">
              audio/ogg
            </ResponseField>

            <ResponseField name="Max Size" type="string">
              16MB
            </ResponseField>

            <ResponseField name="Codec" type="string">
              OPUS only
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="AMR" type="Audio">
          <Expandable title="specifications">
            <ResponseField name="Extension" type="string">
              .amr
            </ResponseField>

            <ResponseField name="MIME Type" type="string">
              audio/amr
            </ResponseField>

            <ResponseField name="Max Size" type="string">
              16MB
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="MP4 Audio" type="Audio">
          <Expandable title="specifications">
            <ResponseField name="Extension" type="string">
              .m4a
            </ResponseField>

            <ResponseField name="MIME Type" type="string">
              audio/mp4
            </ResponseField>

            <ResponseField name="Max Size" type="string">
              16MB
            </ResponseField>
          </Expandable>
        </ResponseField>
      </Expandable>
    </ResponseField>
  </Tab>

  <Tab title="Stickers">
    <ResponseField name="Supported Formats" type="Object">
      <Expandable title="formats">
        <ResponseField name="Static Sticker" type="WebP">
          <Expandable title="specifications">
            <ResponseField name="Extension" type="string">
              .webp
            </ResponseField>

            <ResponseField name="MIME Type" type="string">
              image/webp
            </ResponseField>

            <ResponseField name="Max Size" type="string">
              100KB
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="Animated Sticker" type="WebP">
          <Expandable title="specifications">
            <ResponseField name="Extension" type="string">
              .webp
            </ResponseField>

            <ResponseField name="MIME Type" type="string">
              image/webp
            </ResponseField>

            <ResponseField name="Max Size" type="string">
              500KB
            </ResponseField>
          </Expandable>
        </ResponseField>
      </Expandable>
    </ResponseField>
  </Tab>
</Tabs>

## Template-Based Messaging

Whatsable intelligently selects the appropriate template based on the message content and attachment type.

<Accordion title="Template Selection Logic" icon="wand-magic-sparkles">
  Whatsable automatically selects the appropriate template based on your content:

  * **Text-only messages**: Uses templates like `standard_1_line_textonly`, `standard_2_line_textonly`, etc.
  * **Image attachments**: Uses templates like `standard_image_notification_1_lines`, `standard_image_notification_2_lines`, etc.
  * **Video attachments**: Uses templates like `standard_video_notification_1_lines`, `standard_video_notification_2_lines`, etc.
  * **Document attachments**: Uses templates like `standard_doc_message_1_line`, `standard_doc_message_2_lines`, etc.
</Accordion>

<Note>
  Template messaging ensures your messages maintain consistent formatting and follow WhatsApp guidelines.
</Note>

## Rate Limits and Best Practices

<Steps>
  <Step title="Respect Rate Limits">
    Whatsable enforces rate limits to ensure reliable message delivery. Standard accounts are limited to 50 messages per minute, while enterprise accounts have customizable limits.

    <Warning>
      Exceeding rate limits may result in temporary API access restrictions.
    </Warning>
  </Step>

  <Step title="Implement Error Handling">
    Always implement proper error handling to manage failed message deliveries gracefully:

    ```javascript theme={null}
    try {
      const response = await sendWhatsAppMessage();
      if (!response.success) {
        // Handle specific error based on response message
        console.error('Message sending failed:', response.message);
      }
    } catch (error) {
      // Handle network or server errors
      console.error('API request failed:', error);
    }
    ```
  </Step>

  <Step title="Optimize Media Size">
    Compress images and videos before sending to improve delivery speed and reliability:

    * Resize images to appropriate dimensions for WhatsApp (1080px max width recommended)
    * Compress videos to reduce file size while maintaining quality
    * Use CDN-hosted media when possible rather than base64 encoding
  </Step>
</Steps>

## FAQ

<AccordionGroup>
  <Accordion title="Is Whatsable officially affiliated with WhatsApp?">
    No, Whatsable is not affiliated with or endorsed by WhatsApp Inc. Whatsable uses the WhatsApp Business API to provide its services.
  </Accordion>

  <Accordion title="Do recipients need to opt in before receiving messages?">
    Yes, according to WhatsApp's policy, recipients must explicitly opt in to receive messages from businesses. Ensure you have proper consent before sending messages.
  </Accordion>

  <Accordion title="Can I track message delivery status?">
    Currently, the Whatsable API provides message acceptance status in the response. Real-time delivery and read receipts are planned for a future release.
  </Accordion>

  <Accordion title="Can I send messages to multiple recipients at once?">
    Yes, but you need to send individual API requests for each recipient. Bulk messaging functionality with a single API call is available for enterprise customers.
  </Accordion>
</AccordionGroup>

## Support

<CardGroup>
  <Card title="Live Chat Support" icon="message" href="https://dashboard.whatsable.app/support">
    Click the green chat button in the bottom right corner of the Whatsable dashboard
  </Card>

  <Card title="Email Support" icon="envelope" href="mailto:team@whatsable.app">
    Contact our team at [team@whatsable.app](mailto:team@whatsable.app)
  </Card>
</CardGroup>

<Note>
  Our support team is available Monday through Friday, 9 AM to 6 PM UTC. Enterprise customers receive 24/7 support access.
</Note>

## Updates

<Update label="2023-09-01" description="API v2.0.0 Release">
  <Frame>
    <img alt="API v2.0.0 Release" />

    <img alt="API v2.0.0 Release" />
  </Frame>

  ### What's New

  * **Improved Media Handling**: Support for larger file sizes and more media types
  * **Enhanced Error Reporting**: More detailed error messages and status codes
  * **Better Reliability**: Automatic retry mechanism for failed message delivery
  * **Performance Improvements**: 50% faster message delivery times
</Update>

<Update label="2023-06-15" description="API v1.5.0 Release">
  ### What's New

  * Added support for sticker messages
  * Improved template selection algorithm
  * Fixed issues with document attachments
</Update>

<Tip>
  For a complete changelog, visit the [Whatsable Release Notes](https://dashboard.whatsable.app/changelog) page.
</Tip>

<Warning>
  API v1 is scheduled for deprecation on December 31, 2023. Please upgrade to v2.0.0 before this date.
</Warning>


# Connect WhatsApp Business to Whatsable (Embedded Signup + Coexistence)
Source: https://docs.whatsable.app/guides/whatsable/connect-whatsapp-coexistence

Connect your WhatsApp Business number to Whatsable with Meta Embedded Signup. Keep the WhatsApp Business app on your phone. Meta Coexistence keeps both working on the same number.

# Connect WhatsApp Business to Whatsable (Embedded Signup + Coexistence)

Keep the WhatsApp Business app on your phone and add Whatsable on the same number. Meta calls this **Coexistence**. This guide covers what Coexistence actually means, what to check before you start Embedded Signup, the signup flow at a high level, and what changes (and what doesn't) once you're connected.

## What Coexistence means

Meta Coexistence lets one WhatsApp number run in two places at the same time: the **WhatsApp Business app** on your phone, and **Whatsable** in the background.

* You keep the WhatsApp Business app installed and can keep using it. Connecting to Whatsable does not require removing it.
* Messages sync **both ways**. A reply typed on your phone reaches Whatsable, and a message sent from Whatsable reaches your phone.
* At the QR / Coexistence step, you'll get the option to **share chat history**. Meta may label it **"From last 6 months"**. Choosing it can bring roughly the **last 6 months** of your **1:1** chats into Whatsable (about 180 days), per Meta's own docs.
* **Groups**, **Status**, and **Calls** stay on the WhatsApp Business app. They are **not** synced to Whatsable, no matter what you choose at the chat history step.
* If you skip sharing chat history, that's fine too. Only new messages sync from that point forward.

<Warning>
  Do not uninstall the WhatsApp Business app after you connect. Coexistence depends on the app staying installed on that number.
</Warning>

## Before you start

<Check>
  A **Meta Business Portfolio**. Embedded Signup requires a Business Portfolio, not a personal Facebook profile. You can create one during the flow, but having one ready first is faster. For the website field, a business website is fine, but an Instagram or Facebook page URL also works if you don't have one yet.
</Check>

<Check>
  A phone number with **some recent activity** on it. A brand-new, never-used number may fail Coexistence. The number should also already be registered on the **WhatsApp Business app** (not the consumer WhatsApp app).
</Check>

<Check>
  Confirm your number's country isn't restricted. See [country restrictions](#country-restrictions) below.
</Check>

### Country restrictions

Meta doesn't support new WhatsApp Business Platform connections from **Iran, Cuba, North Korea, Syria**, and **some regions of Ukraine**. If your number is registered in one of these, an existing number can't connect. You'd need a different number outside those restrictions.

### If you're already using an unofficial WhatsApp tool on this number

Turning on Coexistence replaces whatever **unofficial (non-Meta) API tool** was running on that number. Once Coexistence is active, those unofficial tools stop working on it. That's expected.

### Pricing

The phone number itself is **free**. Meta doesn't charge for it. What you pay for is your Whatsable plan; Whatsable passes Meta's conversation costs through at **0% markup**. See [pricing](https://whatsable.app/pricing) for current plans.

## Embedded Signup, at a high level

<Steps>
  <Step title="Start Connect WhatsApp from Whatsable">
    From your Whatsable account, start the Connect WhatsApp flow.
  </Step>

  <Step title="Log in with Facebook">
    Meta's Embedded Signup opens. Log in with the Facebook account tied to your Meta Business Portfolio.
  </Step>

  <Step title="Pick or create your Business Portfolio">
    Select the Meta Business Portfolio this number belongs to, or create one if you don't have one yet.
  </Step>

  <Step title="Pick or create a WhatsApp Business Account">
    Choose an existing WhatsApp Business Account, or let Meta create a new one.
  </Step>

  <Step title="Add your phone number">
    Enter the number you want to connect. If Meta detects that number is already active in the WhatsApp Business app, it offers Coexistence instead of a fresh registration.
  </Step>

  <Step title="Scan the QR code and choose Coexistence">
    Confirm you want to keep the number in the WhatsApp Business app. When asked about your chat history, choose to **share chat history** (Meta may show this as **"From last 6 months"**). That brings roughly the last 6 months of your 1:1 chats into Whatsable. Groups, Status, and Calls stay on the WhatsApp Business app either way. Skipping this step just means only new messages sync from here on.
  </Step>

  <Step title="Finish verification">
    Complete any remaining verification Meta asks for (business verification, payment method) and wait for confirmation.
  </Step>
</Steps>

<Note>
  Embedded Signup runs inside your Whatsable account. Technical footnote: the underlying console lives at `notifyer.whatsable.app`. You may see that domain during signup; it's Whatsable, not a separate product.
</Note>

## After you connect

* If your Meta Business Portfolio is already verified, expect to be able to send your first message in about **20 minutes**.
* Both sides stay live: keep replying from the WhatsApp Business app, and send and receive through Whatsable at the same time.
* Any unofficial API tool that used to run on this number stops working once Coexistence turns on.
* Phone replies typed in the WhatsApp Business app still reach your automations. See [Phone replies in the WhatsApp Business app still hit your webhook](/guides/notifyer-system/api/outbound-whatsapp-app).

## Limits & honesty

* **Throughput is set by Meta, not Whatsable.** Meta enforces a messages-per-second limit on the Cloud API side for every connected number. Whatsable doesn't control or raise this limit. It's the same one any Cloud API number gets from Meta.
* **Country restrictions are Meta's, not Whatsable's.** Numbers registered in Iran, Cuba, North Korea, Syria, or some regions of Ukraine can't complete Embedded Signup today.
* **Each number connects on its own.** Coexistence, and the connection itself, apply per number. There is no cross-number setup step in this guide.

## Troubleshoot

<AccordionGroup>
  <Accordion title="Status is stuck on Pending or shows as not Registered">
    Run Embedded Signup again from Whatsable, using the same number. That clears it most of the time. If it's still stuck after a second attempt, [contact support](mailto:team@whatsable.app).
  </Accordion>

  <Accordion title="Embedded Signup fails with a vague error">
    Messages like *"temporarily prevented..."* or a generic *"An error occurred. Please try again."* don't say what actually went wrong. To see more detail, go to `business.facebook.com`, open **Settings** (bottom left), then **WhatsApp**, and check your **WhatsApp Accounts**. Click the small white arrow next to **Add** (not the Add button itself), then choose **Add WhatsApp Business App**. That path on Meta's side usually surfaces the real error Embedded Signup was hiding, often a Business Portfolio mismatch or a partner lock (see the two items below). It doesn't always spell out which portfolio is the problem, so you may still need to check your portfolios by hand.
  </Accordion>

  <Accordion title="Your Instagram or Facebook page sits on a different Business Portfolio">
    If the Instagram or Facebook page tied to your account belongs to a different Meta Business Portfolio than the one you're using for WhatsApp, Embedded Signup can fail without a clear reason. Connect using the Business Portfolio that actually owns that page, or move the page into the right portfolio first.
  </Accordion>

  <Accordion title="Number is already connected to a partner, or Meta says it's not eligible">
    If this number was previously set up through another Meta Business Partner (BSP), that partner link can block Embedded Signup. Go to `business.facebook.com`, then **Settings**, then **WhatsApp**, then the **Partners** tab. Remove the partner tied to this number and wait a few minutes before retrying. While you're there, also confirm you're using the right Business Portfolio and that Business verification isn't the actual holdup.
  </Accordion>

  <Accordion title="Coexistence isn't offered for my number">
    Confirm the number is registered on the WhatsApp Business app (not the consumer WhatsApp app) and has some recent activity. A brand-new number sometimes needs a day or two of normal use before Meta offers Coexistence.
  </Accordion>

  <Accordion title="Verification failed or got stuck">
    Wait 24 hours and try again with the same number, or try the other verification method (SMS vs. call). Don't uninstall the WhatsApp Business app while you retry.
  </Accordion>

  <Accordion title="My number's country isn't supported">
    Meta doesn't support new WhatsApp Business Platform connections from Iran, Cuba, North Korea, Syria, or some regions of Ukraine. [Contact support](mailto:team@whatsable.app) to talk through options.
  </Accordion>

  <Accordion title="Something went wrong mid-signup and I want to start over">
    A full reset touches your Meta Business Portfolio and WhatsApp Business Account configuration. [Contact support](mailto:team@whatsable.app) rather than trying to undo it yourself.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup>
  <Card title="Phone replies still hit your webhook" icon="mobile" href="/guides/notifyer-system/api/outbound-whatsapp-app">
    Coexistence means WhatsApp Business app replies keep flowing to your automation. See the exact fields to filter on.
  </Card>

  <Card title="Pricing" icon="tag" href="https://whatsable.app/pricing">
    The phone number is free. See current Whatsable plans.
  </Card>

  <Card title="Start your free trial" icon="rocket" href="https://console.notifyer-systems.com/sign-in">
    Create a Whatsable account and start Connect WhatsApp.
  </Card>
</CardGroup>

<Card title="Need help?" icon="headset" href="mailto:support@whatsable.app">
  Our support team can help with Embedded Signup, Coexistence, and connection issues.
</Card>


# Whatsable Features
Source: https://docs.whatsable.app/guides/whatsable/features

Explore the key features of Whatsable

# Whatsable Features

Whatsable provides a simple yet powerful set of features for WhatsApp messaging.

## Core Features

### Message Types

* Text messages
* Media messages (images, documents, audio)
* Location sharing
* Contact sharing

### Message Management

* Message status tracking
* Delivery receipts
* Read receipts
* Message history

### Security

* End-to-end encryption
* API key authentication
* Rate limiting
* IP whitelisting

## Advanced Features

### Bulk Messaging

* Send to multiple recipients
* Custom variables
* Scheduling
* Message templates

### Integration

* REST API
* Webhooks
* SDK support
* Third-party integrations

## Best Practices

* Keep messages concise
* Respect rate limits
* Handle errors gracefully
* Monitor message status

## Next Steps

* Learn about [Integrations](/guides/whatsable/integrations)
* Check out our [API Reference](/api-reference/whatsable)
* Read our [Getting Started](/guides/whatsable/getting-started) guide


# Getting Started with Whatsable
Source: https://docs.whatsable.app/guides/whatsable/getting-started

Learn how to get started with Whatsable, the simple WhatsApp messaging solution

# Getting Started with Whatsable

Whatsable is the simplest way to send WhatsApp messages programmatically. This guide will help you get started with Whatsable in minutes.

## Prerequisites

* A WhatsApp account
* Basic understanding of API integration
* Your Whatsable API key

## Quick Setup

1. Sign up for a Whatsable account
2. Get your API key from the dashboard
3. Start sending messages using our simple API

## First Message

Here's a quick example of sending your first message:

```bash theme={null}
curl -X POST https://dashboard.whatsable.app/api/whatsapp/messages/v2.0.0/send \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+1234567890",
    "message": "Hello from WhatsAble!"
  }'
```

## Next Steps

* Learn about [Features](/guides/whatsable/features)
* Explore [Integrations](/guides/whatsable/integrations)
* Check out our [API Reference](/api-reference/whatsable)


# Whatsable Integrations
Source: https://docs.whatsable.app/guides/whatsable/integrations

Learn how to integrate Whatsable with your applications

# Whatsable Integrations

Integrate Whatsable with your favorite tools and platforms.

## Available Integrations

### No-Code Platforms

* Zapier
* Make (formerly Integromat)
* n8n
* Pipedream

### CRM Systems

* Salesforce
* HubSpot
* Zoho CRM
* Pipedrive

### E-commerce Platforms

* Shopify
* WooCommerce
* Magento
* BigCommerce

## Custom Integration

### REST API

```javascript theme={null}
const axios = require('axios');

const sendMessage = async (to, message) => {
  try {
    const response = await axios.post(
      'https://dashboard.whatsable.app/api/whatsapp/messages/v2.0.0/send',
      {
        to,
        message
      },
      {
        headers: {
          'Authorization': `Bearer ${process.env.WHATSABLE_API_KEY}`,
          'Content-Type': 'application/json'
        }
      }
    );
    return response.data;
  } catch (error) {
    console.error('Error sending message:', error);
    throw error;
  }
};
```

### Webhooks

Configure webhooks to receive real-time updates about your messages:

```json theme={null}
{
  "event": "message.status",
  "data": {
    "message_id": "msg_123",
    "status": "delivered",
    "timestamp": "2024-03-20T10:00:00Z"
  }
}
```

## Best Practices

* Use environment variables for API keys
* Implement retry logic
* Handle rate limits
* Monitor webhook delivery

## Next Steps

* Read our [Getting Started](/guides/whatsable/getting-started) guide
* Explore [Features](/guides/whatsable/features)
* Check out our [API Reference](/api-reference/whatsable)


# Make
Source: https://docs.whatsable.app/guides/whatsable/make

Learn how to automate WhatsApp messaging through Make with Whatsable

# Whatsable Integration with Make

<Frame>
  <img />
</Frame>

<Info>
  This page is the **Whatsable Bot** integration (messages to Whatsable's number). If you need your **own WhatsApp Business number**, including Meta WhatsApp Coexistence (keep the WhatsApp Business app) and webhooks for **outgoing** messages typed on the phone (`incoming_message`, `send_by`, `was_message_by_human`), use [Notifyer System with Make](/guides/notifyer-system/make-overview).
</Info>

## Prerequisites

Before getting started, make sure you have:

<CardGroup>
  <Card title="Whatsable Account" icon="user">
    An active subscription with Whatsable
  </Card>

  <Card title="Make" icon="user">
    Access to [Make](https://www.make.com/en/register/) scenario automation platform
  </Card>
</CardGroup>

<Tip>
  New to Whatsable? [Sign up here](https://dashboard.whatsable.app/signin)
</Tip>

## Get started with Whatsable

<Steps>
  <Step title="Subscribe to Whatsable">
    To use the Whatsable API, you'll need an active subscription:

    1. Log in to your Whatsable dashboard
    2. Click the **Subscribe** button
    3. Start your 7-day free trial

    <Tip>
      During your trial, you can add unlimited phone numbers to test the service. After the trial period, pricing is \$8.99 per month per phone number.
    </Tip>
  </Step>

  <Step title="Add and verify your phone number">
    For Whatsable to send messages through your WhatsApp account:

    1. In your Whatsable dashboard, navigate to **Verified Numbers**
    2. Click **Add New Number**
    3. Enter your phone number (with country code)
    4. You'll receive a WhatsApp verification code
    5. Enter the verification code in the Whatsable dashboard

    <Frame>
      <img alt="Whatsable node selection" />
    </Frame>

    <Note>
      **Multiple numbers?** You only need to complete the verification process for your first phone number. For additional numbers, simply add them and save—no verification required.
    </Note>
  </Step>

  <Step title="Get your API key">
    To connect Whatsable with Make, you'll need your API key:

    1. In your Whatsable dashboard, go to **API Keys**
    2. Copy your unique API key
    3. Store it securely—you'll need it for the integration

    <Warning>
      Never share your API key publicly or commit it to version control systems.
    </Warning>

    <Frame>
      <img alt="Whatsable Api Keys" />
    </Frame>
  </Step>
</Steps>

## Connect Whatsable to Make

Now that you have Whatsable set up, let's connect it to Make to automate your scenarios.

<Steps>
  <Step title="Set up your Make Scenario">
    1. Log in to your Make account
    2. Create a new scenario by clicking **+ Create a new scenario**
    3. (Optional) Add a trigger module of your choice:
       * Popular triggers include Google Forms, Jotform, ClickUp, or a Schedule trigger
       * Connect and configure your trigger according to your use case

    <Frame>
      <img alt="Setting up a module/trigger Make" />
    </Frame>
  </Step>

  <Step title="Add the Whatsable module">
    1. Click the **+** button to add a new module
    2. Search for "Whatsable Message" in the apps or modules library
    3. Select the app with the official Whatsable logo

    <Frame>
      <img alt="Adding the Whatsable module" />
    </Frame>
  </Step>

  <Step title="Configure Whatsable credentials">
    <Accordion title="Credential Setup">
      1. Once you click on Whatsable module, select **Send a WhatsApp Message** from the **ACTIONS** list
      2. Click **Create a connection** in the **Connection** section of Whatsable module and you will be prompted to enter your API Key
      3. Enter your Whatsable API key that you copied earlier
      4. Rename your connection name if needed
      5. Click **Save** to store your credential

      <Frame>
        <img alt="Configuring Whatsable credentials" />
      </Frame>
    </Accordion>
  </Step>

  <Step title="Configure your message">
    Complete the required fields:

    <ResponseField name="Phone" type="string">
      Select the recipient's phone number (In **Your verified WhatsApp number exactly as listed in the dashboard** dropdown, you'll see all phone numbers added in your Whatsable dashboard's **Verified Numbers** menu.)
    </ResponseField>

    <ResponseField name="Message Body" type="string">
      Type your message text or use variables from previous steps
    </ResponseField>

    <ResponseField name="File" type="string">
      <Steps>
        <Step>
          <ResponseField name="Attachment URL (must be publicly available)" type="url">
            Enter publicly accessible media URL for Attachment (image/video/document)

            <Warning>
              Ensure your attachment URLs is publicly accessible and match the supported file formats.
            </Warning>
          </ResponseField>
        </Step>

        <Step>
          <ResponseField name="File Name" type="string">
            Specify a custom filename for your attachment
          </ResponseField>
        </Step>
      </Steps>
    </ResponseField>

    <Frame>
      <img alt="Configuring message" />
    </Frame>
  </Step>

  <Step title="Test and activate your scenario">
    1. Click **Save** to save your message configuration
    2. Right click on the Whatsable module and select **Run this module only** to verify the module is working correctly
       * or click **Run once** in the bottom-left corner of the screen to test the entire scenario
    3. If the test is successful, you'll see a confirmation message
    4. Click **Save** icon in the bottom-left corner to save your scenario (You can also set timer intarval for the scenario)
    5. Toggle the **Active** switch in the bottom-left corner with time to activate your scenario

    <Frame>
      <img alt="Testing and activating your scenario" />
    </Frame>
  </Step>
</Steps>

## Example use cases

<CardGroup>
  <Card title="Customer Onboarding" icon="user-plus">
    Send a welcome message when a new customer signs up
  </Card>

  <Card title="Order Notifications" icon="box-check">
    Update customers when their order status changes
  </Card>

  <Card title="Appointment Reminders" icon="calendar">
    Automatically send reminders before scheduled appointments
  </Card>

  <Card title="Lead Follow-up" icon="user-check">
    Send personalized messages to new leads from your form submissions
  </Card>

  <Card title="Support Ticket Updates" icon="ticket">
    Notify customers when their support ticket status changes
  </Card>
</CardGroup>

## Scenario Diagram

<Frame>
  ```mermaid theme={null}
  flowchart LR
    A[Trigger Module] --> B[Data Transformation]
    B --> C[WhatsAble Module]
    C --> D{Message Sent?}
    D -->|Yes| E[Success Path]
    D -->|No| F[Error Handling]
    E --> G[Additional Actions]
    F --> H[Retry Logic]
  ```
</Frame>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Message not being sent?" icon="circle-exclamation">
    <Steps>
      <Step title="Verify Account Active">
        Verify that your Whatsable account is active.
      </Step>

      <Step title="Phone Number Verification">
        Check that your phone number is properly verified.
      </Step>

      <Step title="API Key in Make">
        Ensure your API key is entered correctly in Make.
      </Step>

      <Step title="Recipient Number Format">
        Confirm that the recipient's phone number is in the correct format (including country code).
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="File attachments not working?" icon="file-exclamation">
    <Steps>
      <Step title="File Size Limit">
        Check that the file size is under 16 MB.
      </Step>

      <Step title="Supported File Type">
        Verify the file type is supported by WhatsApp.
      </Step>

      <Step title="Accessibility">
        Ensure the file path or URL is accessible.
      </Step>
    </Steps>
  </Accordion>
</AccordionGroup>

## Need help?

Our support team is ready to assist you:

<CardGroup>
  <Card title="Email support" icon="envelope" href="mailto:team@whatsable.app">
    Contact [team@whatsable.app](mailto:team@whatsable.app)
  </Card>

  <Card title="Schedule a demo" icon="calendar" href="https://tidycal.com/axelmeta/whatsapp-notifications-by-whatsable">
    Book a personalized walkthrough
  </Card>

  <Card title="Live chat" icon="message-dots" href="https://dashboard.whatsable.app/signin">
    Click the chat button in the bottom right corner of the Whatsable dashboard
  </Card>
</CardGroup>

<Info>
  For additional automation platform integrations (Zapier, n8n, etc.), please contact our support team or check our integration documentation.
</Info>


# n8n
Source: https://docs.whatsable.app/guides/whatsable/n8n

Learn how to automate WhatsApp messaging through n8n with Whatsable

# Whatsable Integration with n8n

<Frame>
  <img />
</Frame>

<Info>
  This page is the **Whatsable Bot** integration (messages to Whatsable's number). If you need your **own WhatsApp Business number**, including Meta WhatsApp Coexistence (keep the WhatsApp Business app) and webhooks for **outgoing** messages typed on the phone (`incoming_message`, `send_by`, `was_message_by_human`), use [Notifyer System with n8n](/guides/notifyer-system/n8n-overview).
</Info>

## Prerequisites

Before getting started, make sure you have:

<CardGroup>
  <Card title="Whatsable Account" icon="user">
    An active subscription with Whatsable
  </Card>

  <Card title="n8n Account" icon="user">
    Access to [n8n](https://app.n8n.cloud/login) workflow automation platform
  </Card>
</CardGroup>

<Tip>
  New to Whatsable? [Sign up here](https://dashboard.whatsable.app/signin)
</Tip>

## Get started with Whatsable

<Steps>
  <Step title="Subscribe to Whatsable">
    To use the Whatsable API, you'll need an active subscription:

    1. Log in to your Whatsable dashboard
    2. Click the **Subscribe** button
    3. Start your 7-day free trial

    <Tip>
      During your trial, you can add unlimited phone numbers to test the service. After the trial period, pricing is \$8.99 per month per phone number.
    </Tip>
  </Step>

  <Step title="Add and verify your phone number">
    For Whatsable to send messages through your WhatsApp account:

    1. In your Whatsable dashboard, navigate to **Verified Numbers**
    2. Click **Add New Number**
    3. Enter your phone number (with country code)
    4. You'll receive a WhatsApp verification code
    5. Enter the verification code in the Whatsable dashboard

    <Frame>
      <img alt="Whatsable node selection" />
    </Frame>

    <Note>
      **Multiple numbers?** You only need to complete the verification process for your first phone number. For additional numbers, simply add them and save—no verification required.
    </Note>
  </Step>

  <Step title="Get your API key">
    To connect Whatsable with n8n, you'll need your API key:

    1. In your Whatsable dashboard, go to **API Keys**
    2. Copy your unique API key
    3. Store it securely—you'll need it for the integration

    <Warning>
      Never share your API key publicly or commit it to version control systems.
    </Warning>

    <Frame>
      <img alt="API Key Location" />
    </Frame>
  </Step>
</Steps>

## Connect Whatsable to n8n

Now that you have Whatsable set up, let's connect it to n8n to automate your workflows.

<Steps>
  <Step title="Set up your n8n workflow">
    1. Log in to your n8n account
    2. Create a new workflow by clicking **+ New Workflow**
    3. Add a trigger node of your choice:
       * Popular triggers include Google Forms, Jotform, ClickUp, or a Schedule trigger
       * Connect and configure your trigger according to your use case

    <Accordion title="Whatsable trigger node (optional)">
      <Info>
        The Whatsable trigger node enables your workflow to respond automatically to incoming WhatsApp messages. This setup is optional but recommended for building reactive communication flows.
      </Info>

      <Steps>
        <Step title="Add Whatsable trigger node">
          Follow these steps to add the Whatsable trigger node to your workflow:

          1. Click the **+** button in your workflow canvas to add a new node
          2. Search for "Whatsable" in the node library search bar
          3. Select the node displaying the official Whatsable logo
          4. From the available trigger options, choose **On new Incoming message event**

          <Frame>
            <img alt="Whatsable node selection showing trigger options" />
          </Frame>

          <Tip>
            The trigger node will automatically listen for incoming messages and initiate your workflow when a new message is received.
          </Tip>
        </Step>

        <Step title="Configure authentication credentials">
          Set up your Whatsable API credentials to establish a secure connection:

          **Webhook URL Configuration:**

          1. In the Whatsable Trigger node parameters, locate the **Webhook URLs** section at the top
          2. Select **Production URL** and copy the generated URL by clicking on it
          3. Store this URL securely as you'll need it for the credential setup

          <Frame>
            <img alt="Production URL selection and copy interface" />
          </Frame>

          **Credential Creation:**

          1. In the **Credential to connect with** dropdown, click **+ Create new credential**
          2. Select **Whatsable Trigger API** as your connection method
          3. Enter your Whatsable API key in the **API Key** field
          4. Paste the Production URL you copied earlier into the **Production URL** field
          5. Assign a descriptive name to your credential (e.g., "Whatsable Production")
          6. Click **Save** to securely store your credentials

          <Frame>
            <img alt="Whatsable credential configuration interface" />
          </Frame>

          <Note>
            Your API credentials are encrypted and stored securely. Never share your API key publicly or commit it to version control.
          </Note>
        </Step>

        <Step title="Test and activate workflow">
          Complete the setup by testing and activating your trigger:

          **Response Configuration:**

          1. In the **Respond** dropdown, select your preferred response timing:
             * **Immediately**: Responds as soon as the trigger fires
             * **When Last Node Finishes**: Waits for the entire workflow to complete before responding

          **Testing:**

          1. Click **Execute step** on the Whatsable node to run a test
          2. Verify the connection is working by checking for a success confirmation
          3. Review any error messages if the test fails and adjust your configuration accordingly

          <Check>
            Once activated, your workflow will automatically process incoming messages according to your configured logic.
          </Check>

          <Warning>
            Remember to test your workflow thoroughly before activating it in production to ensure it behaves as expected.
          </Warning>
        </Step>
      </Steps>
    </Accordion>
  </Step>

  <Step title="Add the Whatsable node">
    1. Click the **+** button to add a new node
    2. Search for "Whatsable" in the node library
    3. Select the node with the official Whatsable logo
    4. After selecting the Whatsable node, choose 'Send message via whatsAble' from the available actions menu

    <Frame>
      <img alt="Whatsable node selection" />
    </Frame>
  </Step>

  <Step title="Configure Whatsable credentials">
    **Credential Setup:**

    1. In the Whatsable node settings, find the **Credential to connect with** dropdown
    2. Select **+ Create new credential**
    3. Enter your Whatsable API key that you copied earlier
    4. Name your credential (e.g., "Whatsable Production")
    5. Click **Save** to store your credential
  </Step>

  <Step title="Configure your message">
    1. In **Resource** dropdown, select **Send Message**
    2. In the **Operation** dropdown, select **Send message via Whatsable**
    3. Complete the required fields:

    <ResponseField name="Recipient Name or ID" type="string">
      Select the recipient's phone number (with country code) previously added in Whatsable
    </ResponseField>

    <ResponseField name="Text" type="string">
      Type your message text or use variables from previous nodes
    </ResponseField>

    <Expandable title="Optional Parameters">
      <ResponseField name="Attachment URL" type="URL">
        Enter the URL of the file, image, or video you want to send with your message
      </ResponseField>

      <ResponseField name="File Name" type="string">
        Specify a custom filename for your attachment
      </ResponseField>
    </Expandable>
  </Step>

  <Step title="Test and activate your workflow">
    1. Click **Test Step** on the Whatsable node to verify it's working correctly
    2. If the test is successful, you'll see a confirmation message
    3. Click **Done** to return to your workflow
    4. Click **Save** to save your entire workflow
    5. Toggle the **Active** switch in the top-right corner to activate your workflow
  </Step>
</Steps>

## Example use cases

<CardGroup>
  <Card title="Customer Onboarding" icon="user-plus">
    Send a welcome message when a new customer signs up
  </Card>

  <Card title="Order Notifications" icon="box-check">
    Update customers when their order status changes
  </Card>

  <Card title="Appointment Reminders" icon="calendar">
    Automatically send reminders before scheduled appointments
  </Card>

  <Card title="Lead Follow-up" icon="user-check">
    Send personalized messages to new leads from your form submissions
  </Card>

  <Card title="Support Ticket Updates" icon="ticket">
    Notify customers when their support ticket status changes
  </Card>
</CardGroup>

## Workflow Diagram

**Sample Whatsable n8n Workflow:**

```mermaid theme={null}
flowchart LR
  A[Trigger Node] --> B[Data Transformation]
  B --> C[WhatsAble Node]
  C --> D{Message Sent?}
  D -->|Yes| E[Success Path]
  D -->|No| F[Error Handling]
  E --> G[Additional Actions]
  F --> H[Retry Logic]
```

## Troubleshooting

<AccordionGroup>
  <Accordion title="Message not being sent?" icon="circle-exclamation">
    **Steps to resolve:**

    1. **Verify Account Active:** Verify that your Whatsable account is active.
    2. **Phone Number Verification:** Check that your phone number is properly verified.
    3. **API Key in n8n:** Ensure your API key is entered correctly in n8n.
    4. **Recipient Number Format:** Confirm that the recipient's phone number is in the correct format (including country code).
  </Accordion>

  <Accordion title="File attachments not working?" icon="file-exclamation">
    **Steps to resolve:**

    1. **File Size Limit:** Check that the file size is under 16 MB.
    2. **Supported File Type:** Verify the file type is supported by WhatsApp.
    3. **Accessibility:** Ensure the file path or URL is accessible.
  </Accordion>
</AccordionGroup>

## Need help?

Our support team is ready to assist you:

<CardGroup>
  <Card title="Email support" icon="envelope" href="mailto:team@whatsable.app">
    Contact [team@whatsable.app](mailto:team@whatsable.app)
  </Card>

  <Card title="Schedule a demo" icon="calendar" href="https://tidycal.com/axelmeta/whatsapp-notifications-by-whatsable">
    Book a personalized walkthrough
  </Card>

  <Card title="Live chat" icon="message-dots" href="https://dashboard.whatsable.app/signin">
    Click the chat button in the bottom right corner of the Whatsable dashboard
  </Card>
</CardGroup>

<Info>
  For additional automation platform integrations (Make.com, Zapier, etc.), please contact our support team or check our integration documentation.
</Info>


# Webhooks
Source: https://docs.whatsable.app/guides/whatsable/webhooks

Receive real-time WhatsApp events. For Notifyer System (your own WhatsApp Business number), webhooks include outgoing messages typed in the WhatsApp Business app — coexistence is supported; you do not delete the app.

<Warning>
  **This page is Whatsable Bot** (messages sent to Whatsable's number). The payload table below is incoming-only.

  If you use **your own WhatsApp Business number** (Notifyer System): [Meta WhatsApp Coexistence](/guides/notifyer-system/embedding-process#whatsapp-coexistence) is supported — you do **not** delete the WhatsApp Business app. Webhooks fire for **incoming and outgoing** messages, including replies typed on the phone. Fields: `incoming_message`, `send_by` (`WhatsApp App` or teammate name), `was_message_by_human`. Full reference: [Message webhooks](/guides/notifyer-system/api/incoming-message).
</Warning>

<Tip>
  Webhooks let your external server react to WhatsApp activity the moment it happens — no polling required. Register an HTTPS endpoint once and Whatsable pushes a JSON payload to it automatically.
</Tip>

<Frame>
  <iframe title="Getting Started with Whatsable Webhooks" />
</Frame>

***

## Whatsable Bot vs Notifier System

Before setting up a webhook, make sure you're using the right product for your use case.

| | **Whatsable Bot (this page)** | **Notifier System** |
| - | - | - |
| **How it works** | You (or a customer) sends a WhatsApp message **to Whatsable's number** → triggers your n8n / Make / Zapier scenario | You send WhatsApp messages **from your own WhatsApp Business number** to your leads or customers |
| **Best for** | Building AI agents, personal automation triggers, developer workflows | Customer outreach, marketing, CRM notifications |
| **Webhook direction** | Inbound — Whatsable calls your endpoint | Inbound and **outgoing** — including replies typed in the WhatsApp Business app |

<Info>
  If you want to **send** messages to leads or customers from your own WhatsApp Business number, use the [Notifier System](/guides/notifyer-system/embedding-process) instead. Notifyer supports [Meta WhatsApp Coexistence](/guides/notifyer-system/embedding-process#whatsapp-coexistence) — you do **not** delete the WhatsApp Business app. Outgoing events (phone app, team inbox, automations) are documented in [Message webhooks](/guides/notifyer-system/api/incoming-message), with `incoming_message`, `send_by`, and `was_message_by_human`.
</Info>

***

## What are Webhooks?

A webhook is an HTTP endpoint you host that Whatsable calls every time a relevant event occurs in your account. Instead of repeatedly asking *"did anything happen?"*, your server receives a real-time `POST` request with the full event payload the instant the event fires.

Common things you can do with Whatsable webhooks:

* Trigger n8n, Make, or Zapier scenarios the moment someone messages your Whatsable bot number
* Build AI agents that react to WhatsApp messages in real time
* Pipe incoming customer messages into your CRM or support desk
* Log chat history to your own database

***

## The Webhooks Dashboard

Navigate to **Operations → Webhooks** (`/operations/webhook`) in your Whatsable dashboard to manage all your registered endpoints.

| Action | How |
| - | - |
| **Add a webhook** | Click **New Webhook** in the toolbar |
| **Search** | Type in the search bar to filter endpoints by URL |
| **Copy a URL** | Click the copy icon next to any endpoint URL |
| **Delete** | Open the ⋮ menu on any row → **Delete** — requires confirmation |

<Info>
  The **Active Webhooks** counter in the toolbar shows how many endpoints are currently registered in your account.
</Info>

### Adding a new endpoint

<Steps>
  <Step title="Open the Add Webhook dialog">
    Click **New Webhook** in the top toolbar of the Webhooks page.
  </Step>

  <Step title="Enter your Endpoint URL">
    Paste the full URL of your server endpoint into the **Endpoint URL** field.
    The URL must begin with `http://` or `https://`. HTTPS is strongly recommended for production.
  </Step>

  <Step title="Save">
    Click **Create Webhook**. Whatsable stores the endpoint and begins routing eligible events to it immediately.
  </Step>
</Steps>

### Deleting an endpoint

<Steps>
  <Step title="Find the webhook">
    Use the search bar or scroll through the table to locate the endpoint you want to remove.
  </Step>

  <Step title="Open the action menu">
    Click the ⋮ icon in the **Actions** column of that row.
  </Step>

  <Step title="Confirm deletion">
    Select **Delete** and confirm in the dialog that appears. Deletion is permanent and cannot be undone.
  </Step>
</Steps>

<Warning>
  Deleting a webhook immediately stops all future event deliveries to that endpoint. Make sure nothing critical depends on the endpoint before removing it.
</Warning>

***

## Webhook Data Model

Every webhook you register is stored with the following fields.

<ResponseField name="id" type="number">
  Auto-incremented integer that uniquely identifies this webhook within your account. Use it to target specific webhooks in API operations.
</ResponseField>

<ResponseField name="webhook" type="string">
  The full endpoint URL Whatsable POSTs events to (e.g. `https://api.example.com/whatsapp/events`). Must be a valid HTTP or HTTPS URL.
</ResponseField>

<ResponseField name="user_id" type="string">
  UUID of the Whatsable account that owns this webhook. Set automatically at creation — you cannot assign a webhook to a different account.
</ResponseField>

<ResponseField name="created_at" type="string">
  ISO 8601 timestamp recording when the webhook was registered. Webhooks are returned in newest-first order by default.
</ResponseField>

***

## Incoming Webhook Payload

When an event fires, Whatsable sends an HTTP `POST` to your endpoint with a `Content-Type: application/json` body.

### Incoming message payload

<CodeGroup>
  ```json Text Message theme={null}
  {
    "last_messages": [
      {
        "type": "user",
        "content": "Can I reschedule my appointment for Thursday?",
        "timestamp": "2025-06-09T22:08:11.990Z",
        "content_type": "text"
      },
      {
        "type": "bot",
        "content": "Of course! Let me pull up available slots for you.",
        "timestamp": "2025-06-09T21:45:30.417Z",
        "content_type": "text"
      }
    ],
    "conversation_paragraph": "User (10:08:11 PM): Can I reschedule my appointment for Thursday? ; Bot (9:45:30 PM): Of course! Let me pull up available slots for you.",
    "phone_number": "14155552671",
    "recipient_name": "Alex Martinez",
    "user_id": "9232fcef-a570-4a2c-b46b-6cab53aec304",
    "last_message_of_user": "Can I reschedule my appointment for Thursday?",
    "last_message_of_bot": "Of course! Let me pull up available slots for you.",
    "message_type": "text",
    "user_last_message_time": 1749506891,
    "bot_last_message_time": 1749504330,
    "attachment_url": null,
    "note": "",
    "note_automation": "",
    "labels": "appointments, rescheduling"
  }
  ```

  ```json Media Message (Document) theme={null}
  {
    "last_messages": [
      {
        "type": "user",
        "content": "",
        "timestamp": "2025-06-09T14:05:12.000Z",
        "content_type": "document",
        "media_url": "https://api.insightssystem.com/vault/contract_v2.pdf"
      },
      {
        "type": "bot",
        "content": "Please send the signed contract when ready.",
        "timestamp": "2025-06-09T14:03:20.000Z",
        "content_type": "text"
      }
    ],
    "conversation_paragraph": "User (2:05:12 PM): [Document] ; Bot (2:03:20 PM): Please send the signed contract when ready.",
    "phone_number": "14155552671",
    "recipient_name": "Alex Martinez",
    "user_id": "9232fcef-a570-4a2c-b46b-6cab53aec304",
    "last_message_of_user": "",
    "last_message_of_bot": "Please send the signed contract when ready.",
    "message_type": "document",
    "user_last_message_time": 1749472312,
    "bot_last_message_time": 1749472200,
    "attachment_url": "https://api.insightssystem.com/vault/contract_v2.pdf",
    "note": "",
    "note_automation": "",
    "labels": "contracts"
  }
  ```
</CodeGroup>

### Payload fields

<ResponseField name="last_messages" type="array">
  Ordered array of recent messages in the conversation, newest last.

  <Expandable title="last_messages item">
    <ResponseField name="type" type="string">
      Sender of this message — `"user"` for the customer or `"bot"` for your Whatsable assistant.
    </ResponseField>

    <ResponseField name="content" type="string">
      Text body of the message. Empty string for media-only messages (image, video, document, audio).
    </ResponseField>

    <ResponseField name="timestamp" type="string">
      ISO 8601 UTC timestamp of when this message was sent.
    </ResponseField>

    <ResponseField name="content_type" type="string">
      Media type of the message. One of: `text`, `image`, `audio`, `video`, `document`, `location`.
    </ResponseField>

    <ResponseField name="media_url" type="string">
      Temporary URL to the media file. Present only when `content_type` is not `text`. URLs expire after **24 hours** — download the file promptly if you need to retain it.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="conversation_paragraph" type="string">
  Human-readable plain-text transcript of the recent exchange. Useful for passing directly to an LLM or storing as a summary without parsing the full `last_messages` array.
</ResponseField>

<ResponseField name="phone_number" type="string">
  The WhatsApp phone number of the customer who sent the message (digits only, no `+` prefix).
</ResponseField>

<ResponseField name="recipient_name" type="string">
  Display name of the customer as stored in their WhatsApp profile. May be empty if WhatsApp has not provided a name.
</ResponseField>

<ResponseField name="user_id" type="string">
  UUID of the Whatsable account that received this message. Matches the `user_id` stored on the webhook registration.
</ResponseField>

<ResponseField name="last_message_of_user" type="string">
  Text of the customer's most recent message. For image, video, and document messages this contains the **caption** if one was provided, otherwise an empty string.
</ResponseField>

<ResponseField name="last_message_of_bot" type="string">
  Text of the last message your system sent to this customer.
</ResponseField>

<ResponseField name="message_type" type="string">
  Type of the **latest** message in the conversation. Same values as `content_type` above: `text`, `image`, `audio`, `video`, `document`, `location`.
</ResponseField>

<ResponseField name="user_last_message_time" type="integer">
  Unix timestamp (seconds) of the customer's last message. Use this to calculate response latency or enforce time-based rules.
</ResponseField>

<ResponseField name="bot_last_message_time" type="integer">
  Unix timestamp (seconds) of your system's last reply to this customer.
</ResponseField>

<ResponseField name="attachment_url" type="string | null">
  URL to the media file if the **latest** message contains media. `null` for text-only messages. Same 24-hour expiry applies.
</ResponseField>

<ResponseField name="note" type="string">
  Free-form text note attached to the conversation. Set manually by agents in Notifyer Chat.
</ResponseField>

<ResponseField name="note_automation" type="string">
  Automation-related notes written by internal workflows. Available for your server to read and act on.
</ResponseField>

<ResponseField name="labels" type="string">
  Comma-separated list of labels assigned to the conversation (e.g. `"sales, premium-inquiry"`). Use these to route events to different handlers in your webhook server.
</ResponseField>

***

## Internal API Reference

The Whatsable dashboard manages webhooks through three authenticated internal endpoints. All requests require a valid **Bearer** token from the active session.

### List webhooks

```
GET /api/webhooks/get
```

Returns all webhooks registered by the authenticated user, sorted newest first.

**Authentication:** `Authorization: Bearer <access_token>`

**Response:** Array of webhook objects.

```json theme={null}
[
  {
    "id": 42,
    "created_at": "2025-06-01T10:22:33.000Z",
    "webhook": "https://api.example.com/events",
    "user_id": "6fb11ff2-d9b2-4560-8437-0fe58ec9f4a6"
  }
]
```

***

### Create a webhook

```
POST /api/webhooks/create
```

Registers a new webhook endpoint.

**Authentication:** `Authorization: Bearer <access_token>`

**Request body:**

<ParamField type="string">
  Full HTTP or HTTPS URL of your endpoint. Must be a valid URL — invalid formats are rejected with a `400` error.
</ParamField>

**Response:**

```json theme={null}
{
  "data": {
    "id": 43,
    "created_at": "2025-06-09T12:00:00.000Z",
    "webhook": "https://api.example.com/events",
    "user_id": "6fb11ff2-d9b2-4560-8437-0fe58ec9f4a6"
  }
}
```

**Error codes:**

| Status | Meaning |
| - | - |
| `400` | `webhook` field missing, empty, or not a valid URL |
| `401` | No valid session token provided |
| `500` | Database error — retry after a short delay |

***

### Delete a webhook

```
DELETE /api/webhooks/delete?id={id}
```

Permanently removes a webhook. The server verifies ownership before deleting — you cannot delete another account's webhooks.

**Authentication:** `Authorization: Bearer <access_token>`

**Query parameter:**

| Parameter | Type | Required | Description |
| - | - | - | - |
| `id` | number | Yes | The `id` of the webhook to delete |

**Response:**

```json theme={null}
{ "success": true }
```

**Error codes:**

| Status | Meaning |
| - | - |
| `400` | `id` query parameter not provided |
| `401` | No valid session token |
| `403` | The webhook exists but belongs to a different account |
| `404` | No webhook found with the given `id` |
| `500` | Database error |

***

## Going to Production

When you're done testing and ready to go live, follow these steps to switch from your test webhook URL to your production endpoint.

<Warning>
  **Do not edit your existing test credential.** Editing a credential that was used for testing can break the connection. Always create a new credential for production.
</Warning>

<Steps>
  <Step title="Pin your test data">
    In your automation tool (n8n, Make, etc.), pin the sample payload you received during testing. This keeps the data structure available to configure downstream nodes even after you swap the endpoint.
  </Step>

  <Step title="Copy your production webhook URL">
    In your automation platform, switch to the **Production** URL for your trigger node and copy it.
  </Step>

  <Step title="Create a new credential — do not edit the existing one">
    In Whatsable, go to **Operations → Webhooks** and click **New Webhook**. Paste the production URL and save.

    In your automation tool, create a **new credential** (e.g. `WhatsAble Bot – Production`) rather than overwriting the test credential. Enter the production webhook URL and your API key, then save.
  </Step>

  <Step title="Update the trigger to use the new credential">
    In your automation trigger node, switch the credential selection from the test credential to the new production one. Your workflow is now live.
  </Step>
</Steps>

<Tip>
  Keep your test credential and test webhook intact — you'll want them next time you need to iterate or debug without touching the live flow.
</Tip>

***

## Endpoint Requirements

<Warning>
  Your endpoint must respond with a `2xx` HTTP status code within **10 seconds**. Responses outside that window are treated as failures.
</Warning>

Your webhook server must:

1. Accept `HTTP POST` requests
2. Parse `application/json` request bodies
3. Respond with `200 OK` (or any `2xx`) promptly to acknowledge receipt
4. Be publicly reachable — `localhost` and private network addresses will not work
5. Use **HTTPS** in production environments

***

## Best Practices

<AccordionGroup>
  <Accordion title="Use HTTPS in production">
    Always verify webhook signatures and use HTTPS endpoints. HTTP may be acceptable for local development only. Whatsable shows a reminder banner on the webhook page: *"Always verify webhook signatures and use HTTPS endpoints for secure communication."*
  </Accordion>

  <Accordion title="Respond fast, process async">
    Return `200 OK` immediately, then process the payload in a background job or queue. Long-running synchronous handlers risk timing out before the work is done.
  </Accordion>

  <Accordion title="Handle duplicate deliveries">
    Network retries can cause the same event to arrive more than once. Use the `user_last_message_time` + `phone_number` combination as an idempotency key to detect and skip duplicates.
  </Accordion>

  <Accordion title="Download media promptly">
    `attachment_url` and `media_url` inside `last_messages` expire after **24 hours**. Download and store media files as soon as you receive the webhook — do not rely on the URL remaining valid later.
  </Accordion>

  <Accordion title="Route by labels and message_type">
    Use the `labels` field and `message_type` to dispatch events to different handlers. For example, route `"document"` types to a contract-processing queue and messages labelled `"support"` to your helpdesk integration.
  </Accordion>

  <Accordion title="Log everything">
    Store the raw payload for every incoming event before processing it. Logs are invaluable for debugging and replaying missed events.
  </Accordion>
</AccordionGroup>

***

## Example Handler

```javascript Node.js / Express theme={null}
const express = require('express');
const app = express();
app.use(express.json());

app.post('/webhook', (req, res) => {
  // Acknowledge immediately
  res.status(200).send('OK');

  // Process asynchronously
  const payload = req.body;
  const { phone_number, message_type, last_message_of_user, labels } = payload;

  console.log(`New ${message_type} from ${phone_number}: "${last_message_of_user}"`);

  if (message_type === 'document' || message_type === 'image') {
    // Download media before the 24-hour URL expires
    downloadMedia(payload.attachment_url);
  }

  if (labels?.includes('support')) {
    forwardToHelpdesk(payload);
  }
});

app.listen(3000);
```

***

## Troubleshooting

<AccordionGroup>
  <Accordion title="n8n / Make trigger not firing at all">
    This is the **most common issue** when setting up the Whatsable bot trigger. When configuring the WhatsApp trigger node in n8n or Make, you must explicitly select **Incoming Messages** as the event type. The option can be easy to miss, especially if the interface has changed recently.

    **What to check:**

    1. Open the trigger node settings in your automation tool
    2. Look for an event type or trigger type selector
    3. Make sure **Incoming Messages** (or equivalent) is selected — not "All Events" or left blank
    4. Save and re-activate the trigger

    If it still doesn't fire after sending a test message, move on to the duplicate webhook check below.
  </Accordion>

  <Accordion title="Already tried everything and it still doesn't work">
    Before spending more time debugging, open **Operations → Webhooks** in the Whatsable dashboard and check how many webhooks you have registered. It's easy to accumulate duplicate entries from previous test attempts. Multiple webhooks registered to different URLs (or stale test URLs) can cause unexpected behaviour.

    **Fix:** Delete any old or duplicate webhook entries, keep only the one that matches your current trigger URL, then test again.
  </Accordion>

  <Accordion title="Webhook not receiving events">
    * Confirm the endpoint is publicly accessible (not `localhost` or behind a firewall)
    * Check your server logs for incoming `POST` requests
    * Verify the webhook is listed and saved correctly in the dashboard
    * Ensure your server returns a `2xx` response — otherwise deliveries may be dropped
  </Accordion>

  <Accordion title="Media URLs returning 404 or expired">
    `attachment_url` and `media_url` values are temporary and expire within **24 hours** of generation. If you receive a 404, the file has expired. Download media immediately on receipt and store it in your own storage.
  </Accordion>

  <Accordion title="Getting 403 when deleting a webhook">
    The `DELETE` endpoint enforces ownership checks. You can only delete webhooks that belong to the currently authenticated user. Make sure you are using the correct account session token.
  </Accordion>

  <Accordion title="Duplicate events arriving">
    Whatsable may redeliver events if your server did not respond with a `2xx` in time. Build idempotency into your handler using `phone_number` + `user_last_message_time` as a composite key.
  </Accordion>
</AccordionGroup>

***

## Next steps

<CardGroup>
  <Card title="API Documentation" icon="code" href="/guides/whatsable/api-documentation">
    Explore the full Whatsable REST API for sending messages, managing contacts, and more.
  </Card>

  <Card title="Integrations" icon="plug" href="/guides/whatsable/integrations">
    Connect Whatsable to Zapier, Make, n8n, and other automation platforms.
  </Card>
</CardGroup>


# Zapier
Source: https://docs.whatsable.app/guides/whatsable/zapier

Learn how to automate WhatsApp messaging through Zapier with Whatsable

# Whatsable Integration with Zapier

<Frame>
  <img />
</Frame>

<Info>
  This page is the **Whatsable Bot** integration (messages to Whatsable's number). If you need your **own WhatsApp Business number**, including Meta WhatsApp Coexistence (keep the WhatsApp Business app) and webhooks for **outgoing** messages typed on the phone (`incoming_message`, `send_by`, `was_message_by_human`), use [Notifyer System with Zapier](/guides/notifyer-system/zapier-overview).
</Info>

## Prerequisites

Before getting started, make sure you have:

<CardGroup>
  <Card title="Whatsable Account" icon="user">
    An active subscription with Whatsable
  </Card>

  <Card title="Zapier" icon="user">
    Access to [Zapier](https://zapier.com/sign-up) workflow automation platform
  </Card>
</CardGroup>

<Tip>
  New to Whatsable? [Sign up here](https://dashboard.whatsable.app/signin)
</Tip>

## Get started with Whatsable

<Steps>
  <Step title="Subscribe to Whatsable">
    To use the Whatsable API, you'll need an active subscription:

    1. Log in to your Whatsable dashboard
    2. Click the **Subscribe** button
    3. Start your 7-day free trial

    <Tip>
      During your trial, you can add unlimited phone numbers to test the service. After the trial period, pricing is \$8.99 per month per phone number.
    </Tip>
  </Step>

  <Step title="Add and verify your phone number">
    For Whatsable to send messages through your WhatsApp account:

    1. In your Whatsable dashboard, navigate to **Verified Numbers**
    2. Click **Add New Number**
    3. Enter your phone number (with country code)
    4. You'll receive a WhatsApp verification code
    5. Enter the verification code in the Whatsable dashboard

    <Frame>
      <img alt="Whatsable node selection" />
    </Frame>

    <Note>
      **Multiple numbers?** You only need to complete the verification process for your first phone number. For additional numbers, simply add them and save—no verification required.
    </Note>
  </Step>

  <Step title="Get your API key">
    To connect Whatsable with Zapier, you'll need your API key:

    1. In your Whatsable dashboard, go to **API Keys**
    2. Copy your unique API key
    3. Store it securely—you'll need it for the integration

    <Warning>
      Never share your API key publicly or commit it to version control systems.
    </Warning>

    <Frame>
      <img alt="Whatsable Api Keys" />
    </Frame>
  </Step>
</Steps>

## Connect Whatsable to Zapier

Now that you have Whatsable set up, let's connect it to Zapier to automate your workflows.

<Steps>
  <Step title="Set up your Zapier Zaps">
    1. Log in to your Zapier account
    2. Create a new Zap by clicking **+ Create** and select **Zaps**/**New Zap**
    3. Add a trigger step of your choice:
       * Popular triggers include Google Forms, Jotform, ClickUp, or a Schedule trigger
       * Connect and configure your trigger according to your use case

    <Frame>
      <img alt="Setting up Zapier Zaps" />
    </Frame>
  </Step>

  <Step title="Add the Whatsable app">
    1. Select the next **Action** step or click the **+** button to add a new step
    2. Search for "Whatsable" in the apps and tools library
    3. Select the app with the official Whatsable logo

    <Frame>
      <img alt="Adding the Whatsable app" />
    </Frame>
  </Step>

  <Step title="Configure Whatsable credentials">
    <Accordion title="Credential Setup">
      1. In the Whatsable app Setup, select **Send WhatsApp Message** in the **Action event** dropdown
      2. Click **Sign In** in the **Account** field and you will be prompted to enter your API Key
      3. Enter your Whatsable API key that you copied earlier
      4. Click **Yes, Continue to Whatsable** to store your credential
      5. Next, click the **Continue** button in the Setup screen to proceed to the **Configure** section

      <Frame>
        <img alt="Configuring Whatsable credentials" />
      </Frame>
    </Accordion>
  </Step>

  <Step title="Configure your message">
    Complete the required fields:

    <ResponseField name="Phone" type="string">
      Select the recipient's phone number (In the **Phone** dropdown, you'll see all phone numbers added in your Whatsable dashboard's **Verified Numbers** menu.)
    </ResponseField>

    <ResponseField name="Message Body" type="string">
      Type your message text or use variables from previous steps
    </ResponseField>

    <ResponseField name="Attachment" type="url">
      Enter public URL of a file, image, or video to send with your message
    </ResponseField>

    <ResponseField name="File Name" type="string">
      Specify a custom filename for your attachment
    </ResponseField>

    <Frame>
      <img alt="Configuring message" />
    </Frame>
  </Step>

  <Step title="Test and activate your Zap">
    1. Click **Continue** and then click **Test step** in the **Test** to verify it's working correctly
    2. If the test is successful, you'll see a confirmation message
    3. Click **Publish** to save your entire Zap
    4. Toggle the **Active** switch in the top-left corner to activate your Zap
  </Step>
</Steps>

## Example use cases

<CardGroup>
  <Card title="Customer Onboarding" icon="user-plus">
    Send a welcome message when a new customer signs up
  </Card>

  <Card title="Order Notifications" icon="box-check">
    Update customers when their order status changes
  </Card>

  <Card title="Appointment Reminders" icon="calendar">
    Automatically send reminders before scheduled appointments
  </Card>

  <Card title="Lead Follow-up" icon="user-check">
    Send personalized messages to new leads from your form submissions
  </Card>

  <Card title="Support Ticket Updates" icon="ticket">
    Notify customers when their support ticket status changes
  </Card>
</CardGroup>

## Workflow Diagram

<Frame>
  ```mermaid theme={null}
  flowchart LR
    A[Trigger Node] --> B[Data Transformation]
    B --> C[WhatsAble App]
    C --> D{Message Sent?}
    D -->|Yes| E[Success Path]
    D -->|No| F[Error Handling]
    E --> G[Additional Actions]
    F --> H[Retry Logic]
  ```
</Frame>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Message not being sent?" icon="circle-exclamation">
    <Steps>
      <Step title="Verify Account Active">
        Verify that your Whatsable account is active.
      </Step>

      <Step title="Phone Number Verification">
        Check that your phone number is properly verified.
      </Step>

      <Step title="API Key in Zapier">
        Ensure your API key is entered correctly in Zapier.
      </Step>

      <Step title="Recipient Number Format">
        Confirm that the recipient's phone number is in the correct format (including country code).
      </Step>
    </Steps>
  </Accordion>

  <Accordion title="File attachments not working?" icon="file-exclamation">
    <Steps>
      <Step title="File Size Limit">
        Check that the file size is under 16 MB.
      </Step>

      <Step title="Supported File Type">
        Verify the file type is supported by WhatsApp.
      </Step>

      <Step title="Accessibility">
        Ensure the file path or URL is accessible.
      </Step>
    </Steps>
  </Accordion>
</AccordionGroup>

## Need help?

Our support team is ready to assist you:

<CardGroup>
  <Card title="Email support" icon="envelope" href="mailto:team@whatsable.app">
    Contact [team@whatsable.app](mailto:team@whatsable.app)
  </Card>

  <Card title="Schedule a demo" icon="calendar" href="https://tidycal.com/axelmeta/whatsapp-notifications-by-whatsable">
    Book a personalized walkthrough
  </Card>

  <Card title="Live chat" icon="message-dots" href="https://dashboard.whatsable.app/signin">
    Click the chat button in the bottom right corner of the Whatsable dashboard
  </Card>
</CardGroup>

<Info>
  For additional automation platform integrations (Make.com, n8n, etc.), please contact our support team or check our integration documentation.
</Info>


# Introduction
Source: https://docs.whatsable.app/index

Enterprise-grade WhatsApp automation solutions for business communication

<div>
  <div>
    <h1>WhatsApp Automation for Every Business</h1>

    <div>
      <p>
        Whatsable (formerly Notifyer System) is a WhatsApp automation product that gives you your own WhatsApp Business number and your brand.
      </p>
    </div>
  </div>
</div>

<div>
  <div>
    <div>
      <h2>Whatsable (formerly Notifyer System)</h2>

      <p>
        Whatsable (formerly Notifyer System) lets you use your own number and your brand on WhatsApp.
      </p>
    </div>

    <div>
      <CardGroup>
        <Card title="Whatsable (formerly Notifyer System)" href="https://console.notifyer-systems.com/sign-in">
          <div />

          <div>
            <div>
              <div />

              <div />

              <img alt="Notifyer System" />
            </div>

            <div>
              <div>
                <span>
                  <span />

                  <span />
                </span>

                <span>Flagship</span>
              </div>
            </div>

            <h3>Your number, your brand</h3>
            <p>Customer WhatsApp on your own WhatsApp Business number.</p>
          </div>
        </Card>
      </CardGroup>
    </div>
  </div>
</div>

<div>
  <div>
    <div>
      <h2>Seamless Integration</h2>

      <p>
        Connect with your favorite automation platforms to build powerful communication workflows without writing a single line of code.
      </p>
    </div>

    <div>
      <div>
        <div>
          <img alt="Zapier" />
        </div>

        <div>
          <img alt="Make" />
        </div>

        <div>
          <img alt="n8n" />
        </div>
      </div>
    </div>
  </div>
</div>

<div>
  <div>
    <div>
      <h2>Key Features</h2>

      <p>
        Whatsable (formerly Notifyer System) is for when customers should see your business on WhatsApp.
      </p>
    </div>

    <div>
      <CardGroup>
        <Card title="Message Templates" icon="file-lines">
          <div>
            <div>
              <i />
            </div>

            <p>Create, save, and reuse approved message templates for consistent communication across all your channels.</p>
          </div>
        </Card>

        <Card title="Detailed Analytics" icon="chart-line">
          <div>
            <div>
              <i />
            </div>

            <p>Track delivery rates, open rates, and user engagement metrics with beautiful real-time dashboards.</p>
          </div>
        </Card>

        <Card title="Workflow Automation" icon="diagram-project">
          <div>
            <div>
              <i />
            </div>

            <p>Set up powerful triggers and actions to automate your entire customer communication journey.</p>
          </div>
        </Card>
      </CardGroup>
    </div>
  </div>
</div>


# Introduction
Source: https://docs.whatsable.app/introduction

Enterprise-grade WhatsApp automation solutions for business communication

<div>
  <div>
    <h1>WhatsApp Automation for Every Business</h1>

    <div>
      <p>
        Whatsable (formerly Notifyer System) is a WhatsApp automation product that gives you your own WhatsApp Business number and your brand.
      </p>
    </div>
  </div>
</div>

<div>
  <div>
    <div>
      <h2>Whatsable (formerly Notifyer System)</h2>

      <p>
        Whatsable (formerly Notifyer System) lets you use your own number and your brand on WhatsApp.
      </p>
    </div>

    <div>
      <CardGroup>
        <Card title="Whatsable (formerly Notifyer System)" href="https://console.notifyer-systems.com/sign-in">
          <div />

          <div>
            <div>
              <div />

              <div />

              <img alt="Notifyer System" />
            </div>

            <div>
              <div>
                <span>
                  <span />

                  <span />
                </span>

                <span>Flagship</span>
              </div>
            </div>

            <h3>Your number, your brand</h3>
            <p>Customer WhatsApp on your own WhatsApp Business number.</p>
          </div>
        </Card>
      </CardGroup>
    </div>
  </div>
</div>

<div>
  <div>
    <div>
      <h2>Seamless Integration</h2>

      <p>
        Connect with your favorite automation platforms to build powerful communication workflows without writing a single line of code.
      </p>
    </div>

    <div>
      <div>
        <div>
          <img alt="Zapier" />
        </div>

        <div>
          <img alt="Make" />
        </div>

        <div>
          <img alt="n8n" />
        </div>
      </div>
    </div>
  </div>
</div>

<div>
  <div>
    <div>
      <h2>Key Features</h2>

      <p>
        Whatsable (formerly Notifyer System) is for when customers should see your business on WhatsApp.
      </p>
    </div>

    <div>
      <CardGroup>
        <Card title="Message Templates" icon="file-lines">
          <div>
            <div>
              <i />
            </div>

            <p>Create, save, and reuse approved message templates for consistent communication across all your channels.</p>
          </div>
        </Card>

        <Card title="Detailed Analytics" icon="chart-line">
          <div>
            <div>
              <i />
            </div>

            <p>Track delivery rates, open rates, and user engagement metrics with beautiful real-time dashboards.</p>
          </div>
        </Card>

        <Card title="Workflow Automation" icon="diagram-project">
          <div>
            <div>
              <i />
            </div>

            <p>Set up powerful triggers and actions to automate your entire customer communication journey.</p>
          </div>
        </Card>
      </CardGroup>
    </div>
  </div>
</div>


# Whatsable Suite with n8n
Source: https://docs.whatsable.app/n8n-overview

Integrate n8n with the Whatsable Suite (Whatsable and Notifyer System) for powerful messaging automation

# Whatsable Suite Integration with n8n

<Frame>
  <img />
</Frame>

<Tip>
  The Whatsable Suite offers a comprehensive set of messaging tools that integrate seamlessly with n8n, enabling powerful automation workflows for businesses of all sizes.
</Tip>

## Overview

The Whatsable Suite comprises powerful messaging platforms—Whatsable and Notifyer System—each designed to meet different business needs while integrating perfectly with n8n's workflow automation capabilities.

<Info>
  This guide introduces the Whatsable Suite and its integration with n8n, helping you select the right platform from the suite for your specific business requirements.
</Info>

## The Whatsable Suite

The Whatsable Suite consists of complementary messaging platforms that integrate with n8n, each designed for different business needs:

<CardGroup>
  <Card href="https://docs.whatsable.app/guides/whatsable/n8n">
    <div />

    <div>
      <div>
        <img alt="Whatsable Logo" />
      </div>

      <h3>Whatsable</h3>
      <p>The Whatsable Bot seamlessly delivers important notifications and alerts to you and your team members, ensuring everyone stays informed.</p>
    </div>
  </Card>

  <Card href="https://docs.whatsable.app/guides/notifyer-system/n8n-overview">
    <div />

    <div>
      <div>
        <img alt="Notifyer System Logo" />
      </div>

      <h3>Notifyer System</h3>
      <p>Our most comprehensive solution, the Notifyer System provides complete messaging capabilities for businesses seeking to communicate with customers and leads while maintaining professional branding.</p>
    </div>
  </Card>
</CardGroup>

# Why Choose Whatsable?

<CardGroup>
  <Card title="Meta-Approved Tech Provider" icon="shield">
    <p>Reliable and secure integration with WhatsApp, backed by Meta's approval.</p>
  </Card>

  <Card title="Instant & Automated Messaging" icon="bolt">
    <p>Send customized WhatsApp messages in real-time with powerful automation.</p>
  </Card>

  <Card title="No-Code & Developer-Friendly" icon="code">
    <p>Flexible integration options for both developers and non-technical users.</p>
  </Card>

  <Card title="Enhanced Business Communication" icon="message">
    <p>Send alerts, confirmations, reminders, and team updates efficiently.</p>
  </Card>
</CardGroup>

## Choosing the Right Platform from the Suite

Selecting the optimal platform from the Whatsable Suite depends on your specific business requirements:

## Whatsable Suite Comparison

<div>
  <table>
    <thead>
      <tr>
        <th>Feature</th>
        <th>Whatsable</th>
        <th>Notifyer System</th>
      </tr>
    </thead>

    <tbody>
      <tr>
        <td>WhatsApp Coexistence</td>
        <td>Uses Whatsable's number</td>
        <td>Supported — keep the WhatsApp Business app; outgoing phone-app messages reach n8n</td>
      </tr>

      <tr>
        <td>Outgoing message webhooks</td>
        <td>Inbound to Whatsable's number</td>
        <td>Incoming and outgoing, with send\_by and was\_message\_by\_human</td>
      </tr>

      <tr>
        <td>Target Business Size</td>
        <td>Small & Startups</td>

        <td>Enterprise</td>
      </tr>

      <tr>
        <td>n8n Integration Ease</td>
        <td>Very Simple</td>

        <td>Moderate</td>
      </tr>

      <tr>
        <td>Business Verification</td>
        <td>Not Required</td>

        <td>Full Official Verification</td>
      </tr>

      <tr>
        <td>Message Templates</td>
        <td>No</td>

        <td>Advanced</td>
      </tr>

      <tr>
        <td>Media Support</td>
        <td>Basic</td>

        <td>Advanced</td>
      </tr>

      <tr>
        <td>Pricing Model</td>
        <td>Subscription</td>

        <td>Enterprise Pricing</td>
      </tr>

      <tr>
        <td>Free Trial</td>
        <td>7 days</td>

        <td>Contact Sales</td>
      </tr>
    </tbody>
  </table>
</div>

## Integrating the Whatsable Suite with n8n

Both platforms in the Whatsable Suite integrate with n8n through a similar workflow pattern:

<Frame>
  <iframe title="Introducing the New Features of N8N Nodes Version 2.3.3" />
</Frame>

<Steps>
  <Step title="Set up platform account">
    Create and configure your account on your chosen WhatsApp platform.
  </Step>

  <Step title="Verify phone number">
    Complete the required verification steps for your WhatsApp number.
  </Step>

  <Step title="Obtain API key">
    Generate an API key from your platform's dashboard.
  </Step>

  <Step title="Configure n8n">
    Add the platform's node in n8n and enter your API credentials.
  </Step>

  <Step title="Build workflow">
    Design your automation workflow with triggers and actions.
  </Step>

  <Step title="Test and activate">
    Test your workflow configuration and activate it for production use.
  </Step>
</Steps>

## Common Use Cases

<CardGroup>
  <Card title="Lead Qualification" icon="user-check">
    <p>Send automated follow-up messages to new leads based on form submissions or website interactions.</p>
  </Card>

  <Card title="Order Notifications" icon="box">
    <p>Keep customers informed at every stage of their order from confirmation to delivery.</p>
  </Card>

  <Card title="Appointment Reminders" icon="calendar">
    <p>Reduce no-shows with automated appointment reminders and confirmations.</p>
  </Card>

  <Card title="Customer Support" icon="headset">
    <p>Route support requests to the right team members and provide instant responses to common questions.</p>
  </Card>

  <Card title="Payment Reminders" icon="credit-card">
    <p>Send timely payment reminders for invoices and subscriptions.</p>
  </Card>

  <Card title="Feedback Collection" icon="star">
    <p>Gather customer feedback after purchases or service interactions.</p>
  </Card>
</CardGroup>

## Sample Workflow: Order Confirmation with Whatsable Suite

Here's how a simple order confirmation workflow might look using the Whatsable Suite with n8n:

<Frame>
  ```mermaid theme={null}
  flowchart LR
    A[Order Placed Trigger] --> B[Get Order Details]
    B --> C[Format Message]
    C --> D{Select Suite Platform}
    D -->|WhatsAble| E[WhatsAble Node]
    D -->|Notifyer System| G[Notifyer System Node]
    E --> H[Send Confirmation]
    G --> H
    H --> I[Update Order Status]
  ```
</Frame>

## Best Practices

<AccordionGroup>
  <Accordion title="Message Content">
    <ul>
      <li>Keep messages concise and focused on a single call-to-action</li>
      <li>Personalize content with customer names and order details</li>
      <li>Use emojis sparingly for emphasis, not decoration</li>
      <li>Include clear opt-out instructions in marketing communications</li>
      <li>Avoid sending multiple messages in quick succession</li>
    </ul>
  </Accordion>

  <Accordion title="Workflow Design">
    <ul>
      <li>Add error handling for failed message delivery</li>
      <li>Include conditional logic for different customer segments</li>
      <li>Test thoroughly with sample data before activating</li>
      <li>Configure appropriate retry logic for temporary failures</li>
      <li>Document your workflow design for future reference</li>
    </ul>
  </Accordion>

  <Accordion title="Compliance">
    <ul>
      <li>Ensure you have explicit consent before messaging customers</li>
      <li>Follow WhatsApp's Business Policy for all communications</li>
      <li>Provide clear opt-out mechanisms in your messaging</li>
      <li>Store customer data securely and in compliance with privacy regulations</li>
      <li>Keep records of consent for compliance purposes</li>
    </ul>
  </Accordion>
</AccordionGroup>

## Getting Started with the Whatsable Suite

Ready to enhance your messaging capabilities with the Whatsable Suite and n8n? Follow our platform-specific integration guides:

<CardGroup>
  <Card title="Whatsable + n8n" icon="rocket" href="https://docs.whatsable.app/guides/whatsable/n8n">
    Quick setup with personal numbers - ideal for small businesses and solopreneurs looking for simple integration.
  </Card>

  <Card title="Notifyer System + n8n" icon="building" href="https://docs.whatsable.app/guides/notifyer-system/n8n-overview">
    Enterprise-grade messaging solution with advanced template capabilities and robust API features.
  </Card>
</CardGroup>

## Need Help Choosing?

<div>
  <div>
    <h3>Schedule a Whatsable Suite Demo</h3>
    <p>Not sure which platform in the Whatsable Suite is right for your business? Our experts can help you make the right choice.</p>

    <a href="https://tidycal.com/axelmeta/whatsapp-notifications-by-whatsable">
      Book a Free Consultation
    </a>
  </div>
</div>

## FAQ

<AccordionGroup>
  <Accordion title="Do I need a business account for the Whatsable Suite?">
    <p>It depends on which platform in the Whatsable Suite you choose:</p>

    <ul>
      <li><strong>Whatsable:</strong> Works with regular numbers - no business account required</li>

      <li><strong>Notifyer System:</strong> Requires complete business API integration</li>
    </ul>
  </Accordion>

  <Accordion title="How does n8n connect to the Whatsable Suite?">
    <p>The Whatsable Suite integrates with n8n through dedicated nodes:</p>

    <ul>
      <li>Each platform has its own dedicated node in the n8n library</li>
      <li>API credentials from your chosen platform are required for connection</li>
      <li>Once connected, you can trigger messaging actions from any n8n workflow</li>
      <li>All platforms support dynamic variables from previous nodes in your workflow</li>
    </ul>
  </Accordion>

  <Accordion title="What media types can I send through the n8n integration?">
    <p>All platforms in the Whatsable Suite support standard media types when integrated with n8n:</p>

    <ul>
      <li><strong>Images:</strong> JPG, PNG (up to 5MB)</li>
      <li><strong>Videos:</strong> MP4, 3GP (up to 16MB)</li>
      <li><strong>Documents:</strong> PDF, DOC, XLSX, etc. (up to 100MB)</li>
      <li><strong>Audio:</strong> MP3, OGG, etc.</li>
    </ul>
  </Accordion>

  <Accordion title="Can I use dynamic content from my n8n workflows?">
    <p>Yes, all platforms in the Whatsable Suite support dynamic content from n8n workflows:</p>

    <ul>
      <li><strong>Whatsable:</strong> Use variables directly in message content with no restrictions</li>

      <li><strong>Notifyer System:</strong> Offers template variables for approved templates and regular variables for non-template messages</li>
    </ul>
  </Accordion>
</AccordionGroup>

## Whatsable Suite Support Resources

Need help with your n8n integration with the Whatsable Suite? We've got you covered:

<CardGroup>
  <Card title="Email Support" icon="envelope" href="mailto:team@whatsable.app">
    Contact our dedicated support team for technical assistance with any platform in the Whatsable Suite
  </Card>

  <Card title="Video Tutorials" icon="video" href="https://www.youtube.com/@nocodeshare/videos">
    Watch step-by-step integration guides for connecting n8n with the Whatsable Suite
  </Card>

  <Card title="Implementation Help" icon="code" href="https://tidycal.com/axelmeta/whatsapp-notifications-by-whatsable">
    Get expert assistance with implementing your n8n workflows with the Whatsable Suite
  </Card>
</CardGroup>

<Note>
  Looking for custom integration solutions or enterprise-level support? Contact our solution engineers at [team@whatsable.app](mailto:team@whatsable.app) for personalized assistance with the Whatsable Suite.
</Note>


# Get Started with Whatsable for monday.com
Source: https://docs.whatsable.app/onboarding/get-started-with-whatsable

Connect WhatsApp Business to your monday boards—from install and Meta setup to templates, workflows, and Live Chat. Includes video walkthrough and free setup offer.

# Whatsable + monday.com

<Frame>
  <iframe title="Whatsable monday.com walkthrough" />
</Frame>

Whatsable connects WhatsApp Business to your monday boards. This guide takes you from zero to a working WhatsApp automation inside monday.

<Tip>
  If you’d rather we set this up for you, [**book a free setup call**](https://tidycal.com/axelmeta/whatsapp-notifications-by-whatsable)—included for all customers, even during the free trial.
</Tip>

***

## Quick setup (3 steps)

<Steps>
  <Step title="Create your Whatsable account">
    Go to [**whatsable.app**](https://www.whatsable.app) and create your account
  </Step>

  <Step title="Connect your WhatsApp Business number">
    Connect your WhatsApp Business number through Whatsable and Meta—the detailed steps are in **[Connect your WhatsApp Business number](#2-connect-your-whatsapp-business-number-with-meta-through-whatsable)** below.
  </Step>

  <Step title="Start automating in monday">
    Install Whatsable from the monday marketplace, then build workflows and use **Live Chat** on your boards. Follow the **[Step-by-step walkthrough](#step-by-step-walkthrough)** from the beginning.
  </Step>
</Steps>

<Info>
  **Full video walkthrough:** [**Watch on YouTube**](https://youtu.be/3cc4uvtF7AY) (same embedded video above).
</Info>

***

## Step-by-step walkthrough

### 1. Install Whatsable on monday

In the [monday marketplace](https://monday.com/marketplace), click **Install Whatsable**. This opens monday and asks for permission to install.

<Accordion title="Step 1 — Give permission to install">
  <Frame>
    <img alt="monday marketplace install permission dialog for Whatsable" />
  </Frame>

  There is a **second step** right after: click **Authorize**. Both steps are needed—if you skip authorization, the integration will not work.
</Accordion>

<Accordion title="Step 2 — Authorize">
  Continue through the authorize flow until it completes.

  <Frame>
    <img alt="Authorize Whatsable Notifyer integration in monday.com" />
  </Frame>

  **What you’ll see if authorization is still pending:** When you open the **Whatsable Live Chat** tab on any board item, you may see a screen asking you to **Connect Whatsable Notifyer**. Click **Open authorization** to finish. If a new tab does not open, click **Retry session**.

  <Frame>
    <img alt="Whatsable successfully connected confirmation in monday.com" />
  </Frame>

  Once authorized, you’ll see a confirmation such as **“Connected successfully to monday.”**
</Accordion>

### 2. Connect your WhatsApp Business number with Meta (through Whatsable)

Inside Whatsable, click [**Connect WhatsApp**](https://notifyer.whatsable.app/onboarding/whatsapp-connection) and follow the flow through **Step 2**.

<Note>
  You can skip or ignore prompts to **subscribe** at first—keep going until **Step 2**, where you’ll see the green **Connect your WhatsApp number** [**button**](https://notifyer.whatsable.app/onboarding/whatsapp-connection).
</Note>

**If your number is not connected yet:** The **Whatsable Live Chat** tab can show a WhatsApp setup screen with a green **Open WhatsApp connection** button. Click it to start the Meta connection flow; if nothing opens in a new tab, use **Retry session**.

<Frame>
  <img alt="Whatsable Connect WhatsApp step before redirect to Meta" />
</Frame>

When you click it, you’ll be sent to Meta to log into your Facebook Business portfolio. From there:

1. **Select your business portfolio**.
2. **Choose** your existing WhatsApp Business Account, or **create** a new one.
3. **Select (or create) a Facebook page**—you don't need to actively use it, it just needs to exist
4. **Select an ad account**.
5. **Choose how to attach a number:**
   * **Option A:** Use a number WhatsApp provides for you (no number of your own needed)
   * **Option B:** **Connect your existing WhatsApp Business number**—either select it if it's already linked, or enter it manually and scan the QR code.

### 3. Add a payment method (do not skip)

WhatsApp messaging from the Cloud API normally requires a **billing method on the WhatsApp side**. Many people skip this—and then sends fail.

<Frame>
  <img alt="Meta Business settings—add payment method for WhatsApp account" />
</Frame>

Typical places to add payment in Meta:

* Open [**business.facebook.com**](https://business.facebook.com/), go to **Settings** (often bottom-left) → **Accounts** → **WhatsApp accounts** → select your **Phone number** → open **Summary** and scroll to **Payment settings** → **Add payment method**.
* Alternatively, explore **Billing** / **Payments** sections in Meta Business Suite or Business Settings until you locate **payment method for WhatsApp** (UI labels change over time).

<Warning>
  If Meta **rejects your card**, contact [**team@whatsable.app**](mailto:team@whatsable.app)—we’ll help troubleshoot.
</Warning>

Even if you already have a payment method for **Ads**, you may still need one **explicitly tied to WhatsApp** / conversation-based billing depending on how your Meta account was set up.

<Frame>
  <img alt="Meta Business payment menu for WhatsApp conversation-based billing" />
</Frame>

### 4. Create your first template

A template is the message format WhatsApp uses when you send something from monday. For example: a welcome message when a lead’s status changes to "Qualified."

To create one:

1. Go to the template area ([**click here**](https://notifyer.whatsable.app/create-template)).
2. Give your template a name.
3. Leave the category as **Marketing** (unless it’s a transactional notification, then use **“Utility”**).
4. Write your message. To insert dynamic fields like a contact’s name, click **Add variable** — for example: `Hi {{1}}, thank you for your interest in {{2}}.`
5. Add **example values** so Meta understands what the variables represent (e.g. **“Alex”** for name, **“Product Name”** for product).
6. Optionally add **buttons** — quick replies like **“Yes, I want info”** or URL buttons that can be static or dynamic per contact.
7. Click **Submit for approval**.

<Frame>
  <img alt="Notifyer WhatsApp template creation menu" />
</Frame>

Meta usually approves templates in under a minute. After being approved, the template will appear in your Monday workflow.

### 5. Set up your AI agent (optional)

Whatsable can run an AI agent beside human replies:

* Give it a **name** (for example **“Lead qualifier”**).
* Describe your **business mission** and paste **product / FAQ knowledge**.
* Define **human handoff** rules—for example *“If a customer mentions a deal over \$5 000, notify a human.”*

When handoff fires, Notifyer/Whatsable can notify you (**Notifyer by Whatsable** mobile apps on [**iOS**](https://apps.apple.com/es/app/notifyer-by-whatsable/id6743722183?l=en-GB) and [**Android**](https://play.google.com/store/apps/details?id=com.chatmobile.chat_mobile)).

The agent can also **follow up proactively** when a conversation goes quiet—within the rules you set.

### 6. Invite your team

You can [**add team members and control what they see**](https://notifyer.whatsable.app/role-management):

| Access type | Meaning |
| - | - |
| **All labels** | Sees every conversation you grant them. |
| **Specific labels** | Only conversations with certain labels—useful when routing by region, product line, or role. Conversations can be **auto-assigned** by label rules according to how you configure the product. |

Access can be changed at any time.

[**Video tutorial here**](https://youtu.be/3cc4uvtF7AY)

### 7. Build your monday workflows

Inside any board, click **+** on the workflows area and compose automations.

#### Outbound: send WhatsApp when monday changes

**Example:** when a lead’s **status** becomes **Qualified**:

1. **Trigger:** Status changes to → **Qualified**.
2. **Action:** Search for **Whatsable** → **Send WhatsApp message** (or equivalent).
3. Pick your **approved template**.
4. **Map columns:** name variable ← name column; **recipient / phone** ← phone column (field names vary by recipe).
5. **Publish.**

<Frame>
  <img alt="monday automation workflow Publish step with Whatsable send message" />
</Frame>

#### Inbound: Update monday when WhatsApp activity happens

Whatsable gives you three inbound triggers:

| Trigger | Use case |
| - | - |
| When you send a message to a new WhatsApp contact | You messaged someone new (e.g. a Facebook Lead Ads contact). Use this to create a new monday item. |
| When you send or receive any WhatsApp message | Use this to log every message into the activity tab of the matching monday item. Pair it with Find matching item (by phone number) to update the right record. |
| When you receive a WhatsApp message from a new number | An inbound lead messages you and isn't in monday yet. Use this to auto-create a new item. |

For "find matching item," select your board and use the phone field to match. Then choose what happens if the item is found or not found.

<Frame>
  <img alt="monday Whatsable inbound workflow with find matching item by phone field" />
</Frame>

### 8. See WhatsApp messages directly inside any monday item

This is one of the most useful parts of Whatsable. Every WhatsApp message your team sends or receives gets logged into the Updates section of the matching monday item — so you have full conversation history right next to the lead's details.

When you open any item, you'll see entries like "Last message by Axel Meta: hi" or "Last message by: Delivery Feedback Request — Hi Joe Harris, could you please give us a feedback…" — with the exact date, time, and the team member or template that sent it. You can like, reply, and mention teammates on each message just like any other monday update.

<Frame>
  <img alt="monday item Updates section showing Whatsable WhatsApp message history" />
</Frame>

### 9. Use the Live Chat view inside monday

For active, two-way conversations, go to **My Work** in monday and expand the sidebar. You'll see **Whatsable Live Chat** as a tab.

Click it — no extra login needed — and you can read and reply to every WhatsApp conversation right inside monday. AI replies are labeled as AI; human replies show which team member sent them.

You can also open the Live Chat as a tab on any individual item (next to Updates, Files, and Activity Log) to see only that contact's conversation.

<Frame>
  <img alt="monday board item Whatsable Live Chat tab next to Updates and Files" />
</Frame>

***

## What you can do

* Send **WhatsApp messages automatically from monday boards**
* Get notified when a contact replies
* **Sync contacts & messages** between WhatsApp and monday
* View full WhatsApp conversations inside any board item — no extra login needed
* See every WhatsApp message logged in the Updates section of each item, with full team attribution
* Run an AI agent that qualifies leads and follows up automatically
* Bulk-message contacts by uploading a CSV (broadcasting)
* Reply on the go with our iOS and Android apps
* Connect with Zapier, Make, or n8n for deeper workflows
* See message analytics and access API keys for custom integrations

***

## Helpful Resources

📖 Documentation: [docs.whatsable.app](https://docs.whatsable.app)

🎬 YouTube tutorials: [youtube.com/@TheWhatsAutomator](https://www.youtube.com/@TheWhatsAutomator)

📧 Support: [team@whatsable.app](mailto:team@whatsable.app)

📅 Free setup call: [Book a session](https://tidycal.com/axelmeta/whatsapp-notifications-by-whatsable)

***

## Need help?

Chat with us directly on [whatsable.app](https://www.whatsable.app) — click the green button in the bottom right corner.

Setup help is completely free for all customers, including during your free trial. If you'd rather have us configure your templates and workflows for you, just [book a call](https://tidycal.com/axelmeta/whatsapp-notifications-by-whatsable).


# Quickstart
Source: https://docs.whatsable.app/quickstart

Start sending automated WhatsApp messages in under 5 minutes

## Getting Started with Whatsable

Whatsable offers two straightforward options to integrate our communication tools into your business workflow:

### Option 1: No-Code Integration Platforms

Connect Whatsable to your existing tools without writing a single line of code using our seamless integration with popular automation platforms:

<div>
  <Card title="Make (formerly Integromat)" href="/guides/whatsable/make">
    <div>
      <div>
        <div>
          <img alt="Make Logo" />
        </div>

        <div>
          <p>Create powerful workflows linking Whatsable with over 1,000 apps</p>

          <div>
            <a href="/guides/whatsable/make">
              Whatsable
            </a>

            <a href="/guides/notifyer-system/make-overview">
              Notifyer System
            </a>
          </div>
        </div>
      </div>
    </div>
  </Card>

  <Card title="Zapier" href="/guides/whatsable/zapier">
    <div>
      <div>
        <div>
          <img alt="Zapier Logo" />
        </div>

        <div>
          <p>Automate message sending based on triggers from 3,000+ connected applications</p>

          <div>
            <a href="/guides/whatsable/zapier">
              Whatsable
            </a>

            <a href="/guides/notifyer-system/zapier-overview">
              Notifyer System
            </a>
          </div>
        </div>
      </div>
    </div>
  </Card>

  <Card title="n8n" href="/guides/whatsable/n8n">
    <div>
      <div>
        <div>
          <img alt="n8n Logo" />
        </div>

        <div>
          <p>Leverage this open-source automation tool for custom workflow creation with Whatsable</p>

          <div>
            <a href="/guides/whatsable/n8n">
              Whatsable Combined Node
            </a>
          </div>
        </div>
      </div>
    </div>
  </Card>
</div>

### Option 2: Direct API Access

For developers and businesses requiring custom solutions, our robust API provides complete control:

* RESTful API: Simple HTTP requests to send and manage WhatsApp messages
* Comprehensive Documentation: Detailed endpoints, parameters, and example requests
* Authentication: Secure API key authentication for all requests
* Webhooks: Receive real-time notifications for message delivery and responses

<Tip>Our API documentation includes code examples in popular programming languages to help you integrate Whatsable functionality directly into your applications.</Tip>

Choose the option that best fits your technical capabilities and business requirements to start sending WhatsApp messages through the Whatsable platform today.


# WhatsApp Cloud API error 130429
Source: https://docs.whatsable.app/whatsapp-error-130429

WhatsApp Cloud API error 130429. Cloud API message throughput has been reached. Match on code and details, not on titles.

# WhatsApp Cloud API error 130429

This page documents WhatsApp Cloud API error `130429`.

Meta will deprecate error titles. Match on `code` and `details`, not on the title in `message`.

Official table: [WhatsApp Cloud API error codes](https://developers.facebook.com/docs/whatsapp/cloud-api/support/error-codes/).

## Match these fields

| Field | Value |
| - | - |
| `code` | `130429` |
| `error_data.details` | Cloud API message throughput has been reached. |

Do not build handlers on titles such as `(#130429) Rate limit hit`. Those titles live inside `message` and will be deprecated.

## Official `details`

Cloud API message throughput has been reached.

## Official next step

The app has reached the API throughput limit.

See Meta [Throughput](https://developers.facebook.com/documentation/business-messaging/whatsapp/throughput).

Try again later, or reduce how often the app sends messages.

## Example from Meta

```json theme={null}
{
  "error": {
    "message": "(#130429) Rate limit hit",
    "type": "OAuthException",
    "code": 130429,
    "error_data": {
      "messaging_product": "whatsapp",
      "details": "Cloud API message throughput has been reached."
    },
    "error_subcode": 2494055,
    "fbtrace_id": "Az8or2yhqkZfEZ-_4Qn_Bam"
  }
}
```

The `message` string is a title. Read `code` and `error_data.details`.

## Related codes

* [131026](/whatsapp-error-131026) — unable to deliver message.
* [131047](/whatsapp-error-131047) — more than 24 hours since the recipient last replied.
* [131049](/whatsapp-error-131049) — not delivered to maintain healthy ecosystem engagement.
* [132001](/whatsapp-error-132001) — template missing in that language or not approved.


# WhatsApp Cloud API error 131026
Source: https://docs.whatsable.app/whatsapp-error-131026

WhatsApp Cloud API error 131026. Unable to deliver message. Match on code and details, not on titles.

# WhatsApp Cloud API error 131026

This page documents WhatsApp Cloud API error `131026`.

Meta will deprecate error titles. Match on `code` and `details`, not on the title in `message`.

Official table: [WhatsApp Cloud API error codes](https://developers.facebook.com/docs/whatsapp/cloud-api/support/error-codes/).

## Match these fields

| Field | Value |
| - | - |
| `code` | `131026` |
| `error_data.details` | Unable to deliver message. Reasons can include the cases below. |

Do not build handlers on titles such as `(#131026) …`. Those titles live inside `message` and will be deprecated.

## Official `details`

Unable to deliver message. Reasons can include:

* The recipient phone number is not a WhatsApp phone number.
* Recipient has not accepted the new Terms of Service and Privacy Policy.
* Recipient using an old WhatsApp version. The recipient must use this WhatsApp version or greater:
  * Android: 2.21.15.15
  * SMBA: 2.21.15.15
  * iOS: 2.21.170.4
  * SMBI: 2.21.170.4
  * KaiOS: 2.2130.10
  * Web: 2.2132.6

## Official next step

Use a non-WhatsApp channel. Ask the WhatsApp user to:

* Confirm that they can send a message to your WhatsApp Business phone number.
* Confirm that they have accepted the latest Terms of Service. **Settings** > **Help**, or **Settings** > **Application information**, will prompt them if they have not accepted the latest terms.
* Update to the latest version of the WhatsApp client.

## Fields to read

Read `code` and `error_data.details`.

Ignore the title inside `message`.

## Related codes

* [131047](/whatsapp-error-131047) — more than 24 hours since the recipient last replied.
* [131049](/whatsapp-error-131049) — not delivered to maintain healthy ecosystem engagement.
* [132001](/whatsapp-error-132001) — template missing in that language or not approved.
* [130429](/whatsapp-error-130429) — Cloud API throughput reached.


# WhatsApp Cloud API error 131037
Source: https://docs.whatsable.app/whatsapp-error-131037

WhatsApp Cloud API error 131037: the 555 business phone needs an approved display name before send. Match on code and details, not titles.

This page documents WhatsApp Cloud API error `131037`.

Meta will deprecate error titles. Match on `code` and `details`, not on the title in `message`.

Official table: [WhatsApp Cloud API error codes](https://developers.facebook.com/documentation/business-messaging/whatsapp/support/error-codes).

## Match these fields

| Field | Value |
| - | - |
| `code` | `131037` |
| `error_data.details` | The 555 business phone number used to send the request does not have an approved display name. |

Do not build handlers on titles such as `(#131037) …`. Those titles live inside `message` and will be deprecated.

## What 131037 means

Official `details`: The 555 business phone number used to send the request does not have an approved display name.

Official next step from Meta: change or approve the 555 business phone number’s display name. See Meta’s [display names](https://developers.facebook.com/documentation/business-messaging/whatsapp/display-names) documentation and [How to change your WhatsApp Business display name](https://www.facebook.com/business/help/338047025165344).

`131037` is a **refusal**. The message is not sent.

In one Observed case, the same code refused both free-form text replies inside an open customer service window and template sends on that number.

Always check account health (and billing) before acting on the code alone. A send error code can be the wrong place to start if the account is unhealthy for another reason. Payment-method failures are typically surfaced under other codes (for example `131042`); do not treat `131037` as a payment error by default.

## Reading `health_status`

Query the **phone-number** node (not the account node; the account node omits the phone-number entity):

```bash theme={null}
GET /{phone-number-id}?fields=health_status
```

The response has one rollup, `can_send_message`, and a list of entities: `PHONE_NUMBER`, `WABA`, `BUSINESS`, and `APP`.

* The rollup takes the worst entity. A healthy account behind an unverified business shows `LIMITED` overall. Read the entities to see which one is at fault.
* `can_send_message` values: `AVAILABLE`, `LIMITED`, `BLOCKED`. `LIMITED` is a steady state for businesses that have not passed verification — not an outage by itself.
* The explanation can be free text. Read both `errors` and `additional_info`. In one Observed case, the `PHONE_NUMBER` entity had no error code; `additional_info` said the display name was not approved yet and that the message limit would increase after approval.
* An `AVAILABLE` entity can still list other errors that do not stop messaging. Treat messaging readiness from `can_send_message` and the phone-number / display-name entities, not from every code on the payload.

## Phone-number node traps

Query (current Meta fields plus one legacy field seen in the case):

```bash theme={null}
GET /{phone-number-id}?fields=status,name_status,new_name_status,code_verification_status,quality_rating,whatsapp_business_manager_messaging_limit,messaging_limit_tier,platform_type,verified_name,is_pin_enabled,account_mode
```

`messaging_limit_tier` is a **legacy** field (Observed in the case table below). Prefer `whatsapp_business_manager_messaging_limit` for current reads.

These fields can look healthy while sends still fail with `131037`. Values Observed on a problem +1 555 number at the same time:

| Field | Example value | Meaning |
| - | - | - |
| `status` | `CONNECTED` | registered and online |
| `code_verification_status` | `VERIFIED` | |
| `platform_type` | `CLOUD_API` | Cloud API number |
| `is_pin_enabled` | `true` | two-step PIN set at registration |
| `name_status` | `AVAILABLE_WITHOUT_REVIEW` | no name review shown as pending |
| `new_name_status` | `AVAILABLE_WITHOUT_REVIEW` | no newer name request waiting |
| `messaging_limit_tier` | `TIER_250` | legacy displayed tier (Observed) |
| `quality_rating` | `GREEN` | |
| `verified_name` | an older name | a newly approved name may not be applied yet |

Signals that can disagree for hours or days on the same account (Observed case; lag timing from Meta support):

* The phone-number node says no review is pending (`AVAILABLE_WITHOUT_REVIEW`).
* `health_status` says the display name is not approved.
* WhatsApp Manager’s Phone numbers tab says “Pending review”.
* Meta emails that a display name was approved.
* The displayed messaging limit looks like a normal tier while the effective cap on that +1 555 number is still tiny.

Meta support’s explanation for the lag in that case: the approval must be “reflected”, which can take **1 to 2 business days**. Treat the approval email, Manager, phone-number node, and health endpoint as independent views until they agree. Confirm on the number you send from: `verified_name` matches the approved name, and health no longer flags an unapproved display name.

The messaging limit Meta displays for a normal number is a ceiling, not a guarantee of the effective limit on a +1 555 number whose display name is still unapproved.

## Meta-provided +1 555 numbers

Meta can provide **+1 555** business phone numbers through Embedded Signup. Per Meta’s Embedded Signup docs, these numbers use a US +1 / 555 pattern, are auto-verified, are limited in how many a business can claim, **must have an approved display name before they can send**, and otherwise behave like standard Cloud API numbers once that gate clears. They are not migratable off the platform the way a number you bring yourself is.

For production and portability, use a **real phone number** you control. Keep a +1 555 number for evaluation if you want, or remove it.

For a specific +1 555 number whose display name was not approved, **Meta support** (this case) stated the WABA remained subject to a messaging limit of **five messages per day**, and that the limit would lift once the display name was approved and reflected (often 1 to 2 business days). That five-per-day figure and the reflect timing are **not** documented in Meta’s public error or 555 pages checked for this guide — attribute them to Meta support. Meta’s own docs say a 555 number can send after display-name approval (subject to normal quality, pricing, and messaging limits). Do not treat “never scales” third-party claims as Meta fact.

Observed pattern that fits a tiny cap: five messages went out on day one, then later sends failed with `131037`. The exact reset rule for that five-message limit (calendar day, rolling window, or total) was **not confirmed**.

## Traps

1. **Two accounts with the same name.** The account selector can show two WhatsApp Business Accounts with the same display name and different IDs. An approval email that names the account by name alone does not tell you which ID it applies to. Compare account IDs.
2. **The approval email names the account, not the number.** Display names are tracked per phone number. Confirm on the number you are actually sending from.
3. **A pending display name can block sends** on some numbers after an earlier period of successful sends.
4. **Tell Meta support the number starts with +1 555.** Give the phone number ID in the first message.
5. **Paste IDs and timestamps when you cannot attach screenshots.** If you cannot attach files, paste the exact error text, the phone number ID, the account ID, and each failure’s timestamp. A Graph API `fbtrace_id` helps when your sending tool still has it; Meta can often locate failures from the phone number ID and timestamps without it.

## What to do

1. **For anything customer-facing, use your own real phone number.** Any number that can receive a verification call or SMS works. Keep the +1 555 number for evaluation, or remove it.
2. **Submit a display name early** (on the 555 while you evaluate, and on the real number before you go live). Meta support described approval and reflection as taking one to two business days in the case above.
3. **Complete business verification** if you need higher messaging limits than Meta’s starting unverified tier. Prefer Meta’s current messaging-limits documentation over older tier ladders.
4. **Before scaling, confirm the effective limit**, not only the displayed tier. Send a small batch and check for failures.
5. **Confirm beyond the approval email.** On the phone-number node, check that `verified_name` is the approved name, and that `health_status` no longer says the name is unapproved.

## Reproduce outside your software

To see whether a refusal comes from Meta or from your sending tool, replay one send with a tool you control (Postman, or Meta’s Graph API Explorer).

```bash theme={null}
POST https://graph.facebook.com/v21.0/{phone-number-id}/messages
Authorization: Bearer {token}
Content-Type: application/json
```

```json theme={null}
{
  "messaging_product": "whatsapp",
  "recipient_type": "individual",
  "to": "<recipient number, digits only>",
  "type": "text",
  "text": { "preview_url": false, "body": "test" }
}
```

In Graph API Explorer: choose your app, User Token, add `whatsapp_business_management` and `whatsapp_business_messaging`, generate an access token, and allow the correct WhatsApp Business Account when asked. Keep the token out of support chats.

If the call fails with `131037`, the refusal is Meta’s for that number. The response includes a trace ID. If it succeeds, the difference lies in the original sender.

On a capped +1 555 number, each test message spends the allowance.

## Related codes

* [131026](/whatsapp-error-131026) — unable to deliver message.
* [131047](/whatsapp-error-131047) — more than 24 hours since the recipient last replied.
* [131049](/whatsapp-error-131049) — not delivered to maintain healthy ecosystem engagement.
* [132001](/whatsapp-error-132001) — template missing in that language or not approved.
* [130429](/whatsapp-error-130429) — Cloud API throughput reached.


# WhatsApp Cloud API error 131047
Source: https://docs.whatsable.app/whatsapp-error-131047

WhatsApp Cloud API error 131047. More than 24 hours since the recipient last replied. Match on code and details, not on titles.

# WhatsApp Cloud API error 131047

This page documents WhatsApp Cloud API error `131047`.

Meta will deprecate error titles. Match on `code` and `details`, not on the title in `message`.

Official table: [WhatsApp Cloud API error codes](https://developers.facebook.com/docs/whatsapp/cloud-api/support/error-codes/).

## Match these fields

| Field | Value |
| - | - |
| `code` | `131047` |
| `error_data.details` | More than 24 hours have passed since the recipient last replied to the sender number. |

Do not build handlers on titles such as `(#131047) …`. Those titles live inside `message` and will be deprecated.

## Official `details`

More than 24 hours have passed since the recipient last replied to the sender number.

## Official next step

Send the recipient a [template message](https://developers.facebook.com/documentation/business-messaging/whatsapp/templates/overview) instead.

## Related codes

* [131026](/whatsapp-error-131026) — unable to deliver message.
* [131049](/whatsapp-error-131049) — not delivered to maintain healthy ecosystem engagement.
* [132001](/whatsapp-error-132001) — template missing in that language or not approved.
* [130429](/whatsapp-error-130429) — Cloud API throughput reached.


# WhatsApp Cloud API error 131049
Source: https://docs.whatsable.app/whatsapp-error-131049

WhatsApp Cloud API error 131049. Message not delivered to maintain healthy ecosystem engagement. Match on code and details, not on titles.

# WhatsApp Cloud API error 131049

This page documents WhatsApp Cloud API error `131049`.

Meta will deprecate error titles. Match on `code` and `details`, not on the title in `message`.

Official table: [WhatsApp Cloud API error codes](https://developers.facebook.com/docs/whatsapp/cloud-api/support/error-codes/).

## Match these fields

| Field | Value |
| - | - |
| `code` | `131049` |
| `error_data.details` | This message was not delivered to maintain healthy ecosystem engagement. |

Do not build handlers on titles such as `(#131049) …`. Those titles live inside `message` and will be deprecated.

## Official `details`

This message was not delivered to maintain healthy ecosystem engagement.

## Official next step

If you receive this error and suspect it is due to the limit, wait at least 24 hours before resending the template message.

An immediate retry can return the same error. The limit may stay in effect for differing periods of time.

See [Per-User Marketing Template Message Limits](https://developers.facebook.com/documentation/business-messaging/whatsapp/templates/marketing-templates/per-user-limits).

## Related codes

* [131026](/whatsapp-error-131026) — unable to deliver message.
* [131047](/whatsapp-error-131047) — more than 24 hours since the recipient last replied.
* [132001](/whatsapp-error-132001) — template missing in that language or not approved.
* [130429](/whatsapp-error-130429) — Cloud API throughput reached.


# WhatsApp Cloud API error 132001
Source: https://docs.whatsable.app/whatsapp-error-132001

WhatsApp Cloud API error 132001. Template missing in that language or not approved. Match on code and details, not on titles.

# WhatsApp Cloud API error 132001

This page documents WhatsApp Cloud API error `132001`.

Meta will deprecate error titles. Match on `code` and `details`, not on the title in `message`.

Official table: [WhatsApp Cloud API error codes](https://developers.facebook.com/docs/whatsapp/cloud-api/support/error-codes/).

## Match these fields

| Field | Value |
| - | - |
| `code` | `132001` |
| `error_data.details` | The template does not exist in the specified language or the template has not been approved. |

Do not build handlers on titles such as `(#132001) …`. Those titles live inside `message` and will be deprecated.

## Official `details`

The template does not exist in the specified language or the template has not been approved.

## Official next step

Make sure the template has been approved.

Make sure the template name and language locale are correct.

See Meta [Templates](https://developers.facebook.com/documentation/business-messaging/whatsapp/templates/overview).

## Related codes

* [131026](/whatsapp-error-131026) — unable to deliver message.
* [131047](/whatsapp-error-131047) — more than 24 hours since the recipient last replied.
* [131049](/whatsapp-error-131049) — not delivered to maintain healthy ecosystem engagement.
* [130429](/whatsapp-error-130429) — Cloud API throughput reached.