Refresh lead activity when work changes
When an Onedesk update changes what you need to know about a prospect, use its webhook payload to request the known lead's current visit history.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
Lead activity can be checked too early and then become stale while a support issue or project is still moving.
- Tie a visit-history refresh to a meaningful work update.
- Avoid relying on an old activity review when a ticket or project changes.
- Keep the check limited to a known Leadfeeder lead.
Setup
Build it in a few focused steps.
- 1Connect Onedesk and Leadfeeder to Notis once in the portal.
- 2Create an automation and describe the update signal your backend will send to Notis.
- 3Use one plain-language prompt asking Notis to retrieve visits for the known Leadfeeder lead identifier included with that Onedesk update.
- 4Select an incoming webhook trigger and a channel for run reports.
- 5Send one real update with a valid lead identifier and check the refreshed history.
Questions about this workflow
Does Notis watch Onedesk updates directly?
No. Send the relevant update to a Notis webhook from your backend.
Does this guarantee visits newer than the last check?
The action retrieves visit history. Ask the report to show the returned date range and avoid assuming that new visits exist.
When this happens · Trigger
Do this · Action
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.
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.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
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.
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.
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.