Keep priority prospect follow-up ready
Use a recurring schedule to prepare sales content for a priority prospect list you supply. Notis can ask Autobound to generate drafts when each contact and user detail is confirmed.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Generate Personalized Content
Tool to generate hyper-personalized sales content. Use after confirming contact and user details.
Why this helps
Priority prospects can lose momentum when follow-up depends on someone remembering to prepare the next message.
- Create a recurring prompt to prepare sales content for a supplied priority list.
- Reduce the chance that planned follow-up slips from view.
- Keep recipient details explicit before content generation.
Setup
Build it in a few focused steps.
- 1Connect Autobound once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis from any channel.
- 3In one instruction, ask Notis to generate personalized Autobound content for the priority prospects you provide, after confirming contact and user details.
- 4Pick a recurring schedule trigger and choose where run reports should go.
- 5Test with one real prospect and confirmed contact and user details.
Questions about this workflow
Where does the priority prospect list come from?
Provide the list or its details in your instruction or connected context. The listed trigger and action do not specify a separate list source.
Does a schedule send the content?
No. The available action generates personalized content; the schedule starts the run but does not send it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Autobound. A trigger fires from one place; an action lands in another.
Jira triggers
Autobound actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Generate Insights
Tool to generate ranked prospect or company insights. Use after resolving identifiers to retrieve the most relevant insights.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Generate Personalized Content
Tool to generate hyper-personalized sales content. Use after confirming contact and user details.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
New Project
Triggered when a new project is added in Jira
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Connect any two apps with Notis in the middle.
Jira and Autobound, 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 Autobound.