Carry outreach interest into Docsbot follow-up
When outreach opens a customer conversation, keep the useful details close to support. Send a request to Notis and capture relevant lead information in Docsbot.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Capture Conversation Lead
Saves lead information in conversation metadata, whether or not the conversation exists.
Why this helps
Outreach replies can contain product questions or support needs that are easy to miss when the relationship is tracked only in Affinity.
- Keep relevant outreach context available to support.
- Avoid re-entering lead details by hand.
- Create a consistent handoff from relationship work to customer follow-up.
Setup
Build it in a few focused steps.
- 1Connect Affinity and Docsbot in the Notis portal once.
- 2Create an automation in Automations, New Automation, and name the handoff.
- 3In one instruction, tell Notis how to assess the Affinity outreach details in the incoming request and capture relevant customer interest as a Docsbot lead.
- 4Pick the Notis webhook trigger and choose where run reports should go.
- 5Test with one real outreach response and check the Docsbot lead details.
Questions about this workflow
What starts this workflow?
An HTTP request to the Notis webhook starts it. Affinity has no trigger events listed in this package, so the request must carry or make available the outreach context to assess.
Will it save every outreach reply?
You define which replies count as customer interest in the instruction. The workflow should only capture relevant information that is present in the request or accessible to Notis.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Affinity to Docsbot ai. A trigger fires from one place; an action lands in another.
Affinity 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.
Affinity 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.