Add company context to chatbot ticket handoffs
When an AI agent or chatbot creates a ticket, check the visitor IP for available company information before the ticket reaches your review queue.
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
Automated ticket creation saves time, but a founder may still need to investigate who the visitor represents before deciding what to do.
- Add an optional company profile to AI-generated ticket reports.
- Reduce research after the chatbot has already created the request.
- Keep the lookup connected to the ticket handoff.
Setup
Build it in a few focused steps.
- 1Connect Onedesk and Leadfeeder to Notis once in the portal.
- 2Have your chatbot backend send the new ticket context and visitor IP to a Notis webhook.
- 3Create an automation with one prompt asking Notis to look up company information for that IP and report any match with the ticket context.
- 4Select an incoming webhook trigger and choose where run reports go.
- 5Test with one real chatbot-created ticket and check the lookup result.
Questions about this workflow
Does this change the Onedesk ticket?
The listed action looks up company details in Leadfeeder. The report can provide context for your ticket handling.
Will it always find a company?
No. Leadfeeder can return no match for an IP.
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.