Make abuse reports available in Docsbot
Turn a report URL from an incoming alert into a source your support bot can reference.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create Bot Source
Creates a source for a bot’s knowledge base.
Why this helps
Useful incident reports can stay buried in alerts, leaving support without a searchable reference.
- Add a report URL supplied with an incoming webhook to a bot's sources.
- Make selected threat intelligence available for later bot searches.
- Avoid manually copying report links into the bot's knowledge base.
Setup
Build it in a few focused steps.
- 1Connect Abuselpdb and Docsbot ai once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for adding abuse report sources.
- 3In one instruction, ask Notis to use the report URL from each incoming payload to create a source for the selected Docsbot bot.
- 4Pick the Notis webhook trigger and choose where run reports should go.
- 5Send one real webhook containing a report URL and review the source creation result.
Questions about this workflow
What information must the webhook provide?
It must include a report URL that Docsbot can use as a source, along with the context needed to identify the intended bot.
Can this upload a local report file?
This workflow uses a report URL. File sources require the separate upload URL and file upload steps before creating a source.
Does adding a source mean it is immediately searchable?
The listed action creates a source. Check its processing status in Docsbot before relying on it in a bot response.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Abuselpdb to Docsbot ai. A trigger fires from one place; an action lands in another.
Abuselpdb triggers
Docsbot ai actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Bot
Creates a bot within a team.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Capture Conversation Lead
Saves lead information in conversation metadata, whether or not the conversation exists.
Delete Bot
Permanently deletes a bot; this action cannot be undone.
Generate Conversation Ticket
Turns a Chat Agent conversation into a structured support ticket.
Create Bot Source
Creates a source for a bot’s knowledge base.
Get Bot Details
Retrieves details about a bot in a team.
Create Webhook
Creates a bot webhook subscription; its target must be publicly accessible and support HTTPS.
Get Team Details
Retrieves details about a team, including its members and settings.
Connect any two apps with Notis in the middle.
Abuselpdb and Docsbot ai, 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 Docsbot ai.