Connect Whatsapp to Elorus

When something happens in Whatsapp, Notis takes the next step in Elorus. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Whatsapp to Elorus

View example

Turn WhatsApp invoice requests into Elorus drafts

Recognize a customer's invoice request in WhatsApp, gather the details they supplied, and create an Elorus invoice when the required information is available.

View example

Create an Elorus invoice after a WhatsApp approval

When a customer responds to an interactive WhatsApp prompt, check the conversation for a clearly approved quote and create an invoice only when the needed details are present.

View example

Check Elorus for clients named in WhatsApp inquiries

When an inbound WhatsApp message appears to come from a prospective client, search Elorus contacts to help identify whether the sender is already on file.

View example

Turn WhatsApp expense details into an Elorus draft

Identify expense receipts or expense details shared through WhatsApp, categorize only when supported by the message, and create an Elorus expense from available line items.

View example

Review Elorus expenses against WhatsApp receipts

On a schedule, review recent Elorus expenses and compare them with WhatsApp receipt messages available to the automation, reporting potential gaps without changing records.

View example

Answer balance questions with an Elorus contact lookup

When a WhatsApp customer asks about their balance, identify the matching Elorus contact and retrieve current contact details for a grounded response report.

View example

Find Elorus invoices for WhatsApp billing questions

When a customer asks about an invoice in WhatsApp, search Elorus invoices and report likely matches for review, using the identifiers available in the message.

View example

Check Elorus email templates after WhatsApp template review changes

When a WhatsApp message template review status changes, retrieve Elorus email templates and include the available template list in a report for your review.

View example

Email an existing Elorus invoice after WhatsApp delivery confirmation

When WhatsApp reports a message status change, check whether the message context identifies an existing invoice and authorized email recipient before emailing that invoice through Elorus.

Supported Triggers and Actions

Notis builds workflows that link Whatsapp to Elorus. A trigger fires from one place; an action lands in another.

Whatsapp triggers

Elorus actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Create Invoice

Create an invoice or receipt, saved as a draft by default.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Create Expense

Creates an expense from categorized line items.

ActionInstant

Message Status Updated

Returns no results; message status changes are delivered through webhooks in real time.

TriggerPolling

CREATE_PRODUCT

Create a product or service in the catalog.

ActionInstant

Email Invoice

Email an existing invoice to selected contacts.

ActionInstant

Get Bills

Retrieve bills for viewing and managing expenses or purchases.

ActionInstant

Delete Invoice

Permanently deletes a draft invoice; issued invoices cannot be deleted.

ActionInstant

Get Contacts

Retrieve your contacts.

ActionInstant

Get Credit Notes

Retrieve credit notes.

ActionInstant

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.