Add company context to new support requests
Give each support handoff a little more context by checking the request's IP against Leadfeeder when your backend sends it to Notis.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
A founder handling support and sales may have to stop triaging a request to manually identify the company behind a visitor IP.
- Reduce manual company research during ticket triage.
- Give the next person handling a request a relevant company profile when Leadfeeder finds a match.
- Keep the lookup attached to a specific incoming support event.
Setup
Build it in a few focused steps.
- 1Connect Onedesk and Leadfeeder to Notis once in the portal.
- 2Create a new automation in the portal, or ask Notis to create it conversationally.
- 3Use one plain-language prompt: when your backend sends a new Onedesk request and its visitor IP to Notis, look up the company in Leadfeeder and include the profile in the run report.
- 4Select an incoming webhook trigger and choose a channel for run reports.
- 5Send one real request through the webhook and check the resulting lookup.
Questions about this workflow
Does Onedesk start this automation directly?
No. Onedesk has no integration trigger events here. Your backend sends the request to a Notis webhook.
What if Leadfeeder has no company match for the IP?
The lookup can return no match. Have the prompt report that outcome without treating it as a confirmed company profile.
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.