Skip to content
Notis

Connect Onedesk to Leadfeeder

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

When this happens · Trigger

Do this · Action

Examples

Ways Notis can move work from Onedesk to Leadfeeder

View example

Enrich a new support request with company context

When a new Onedesk support request reaches your backend, use its visitor IP to look up the company in Leadfeeder and return the available company profile for the support handoff.

View example

Review website visits after a ticket escalation

When an Onedesk escalation is sent to a Notis webhook with a Leadfeeder lead identifier, retrieve that lead's visit history to inform the escalation review.

View example

Check Leadfeeder account access weekly

On a weekly schedule, retrieve the Leadfeeder accounts available to the connected user and report the list for a lightweight access check alongside your Onedesk operating routine.

View example

Get a daily digest of custom feed configurations

On a daily schedule, retrieve the custom feed configurations for a confirmed Leadfeeder account and report them as a quick reference for your Onedesk and sales routine.

View example

Add company context to project intake

When a new Onedesk project intake includes a visitor IP and reaches a Notis webhook, look up the company in Leadfeeder and include any match in the intake report.

View example

Review priority lead visits each week

On a weekly schedule, retrieve Leadfeeder visit histories for known priority leads listed in your Onedesk review input and summarize their activity for follow-up planning.

View example

Refresh visit history after a lead-related update

When a lead-related Onedesk update is sent to a Notis webhook with a known Leadfeeder lead, retrieve that lead's visit history for a timely context refresh.

View example

Check custom feed coverage weekly

On a weekly schedule, retrieve custom feeds for a confirmed Leadfeeder account and compare the list in the report with the feed names your Onedesk team expects to review.

View example

Enrich webinar follow-up context from a support request

When a webinar-related Onedesk request is sent to Notis with a visitor IP, retrieve the Leadfeeder company profile, if available, for the follow-up context.

Supported Triggers and Actions

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

Onedesk triggers

Leadfeeder actions

Recurring trigger

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

TriggerScheduled

Get Accounts

Tool to retrieve a list of accounts the user has access to. use when you need to discover all available leadfeeder accounts after authentication.

ActionInstant

Webhook trigger

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

TriggerInstant

Get All Visits

Tool to retrieve all visits for a specific lead. use when you need detailed visit history for a lead, optionally filtered by date range.

ActionInstant

Get Company Info by IP

Tool to retrieve company information based on an ip address. use when you need to enrich an ip and obtain its company profile. returns 404 if no match is found.

ActionInstant

Get Custom Feeds

Tool to retrieve a list of custom feeds for a specific account. use after confirming the account id to list all its custom feed configurations.

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.

Notis

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.

  • Full run history with inputs, outputs and traces
  • Replay any run with edited inputs
  • Approval inbox, confirm via chat in one tap
  • Audit logs for compliance teams

Automations

Inbox

All12Manager5Telegram1Messages0Whatsapp2Email4Slack8

Migrate background jobs to a durable queue You can cancel it through Stripe

3 days

Notis v3 release update This one’s v3: Notis Manager (desktop app with …

8 days

Add multi-tenant RBAC User initiates a voice call

13 days

Draft pricing v (tiers, limits, overages) and sanity-check margins

2 weeks

Verify analytics events for new features That’s a really interesting automat…

1 month

Everything in the box.

Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.

AI in the middle

Every step can include an LLM call: summarise, classify, extract, rewrite.

Full observability

Every run, every step, every input, all replay-able from Mission Control.

Human in the loop

Pause for approval. Notis pings you in chat with one-tap approve.

Self-healing

When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.

Related pairs

More ways to connect Onedesk and Leadfeeder

Connect any two apps with Notis in the middle.

Onedesk and Leadfeeder, or any other combination from 1,000+ integrations.

When this happens · Trigger

Do this · Action

Save your first hour today.

7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Leadfeeder.