Auto-Archive Customer Context
Customer issue closes but context disappears. Notis automatically extracts customer background, preferences, and history--archiving it so you have instant recall when they come back.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Action
Query Data
Tool to query structured data as json from a web page using an agentql query or natural language prompt. use after defining your query or prompt and a url or html.
Why this helps
Customer issue closes. All the context--their background, preferences, history, links--is now buried in a closed issue. Months later when they return, you have to hunt through old issues to remember who they are.
- Customer history never disappears
- Faster context lookup for returning customers
- Build customer profiles over time
- Better serve long-term relationships
Setup
Build it in a few focused steps.
- 1Connect Linear and Agentql to Notis (one-time).
- 2Tell Notis: 'When a customer issue moves to closed, extract all customer context from the issue (name, company, preferences, interaction summary), and save it to an archive document (Google Doc, Notion, etc.)' or create via portal.
- 3Set trigger to Issue Updated (status) on customer issues and pick your team/project.
- 4Choose Slack/email for reports.
- 5Close a test customer issue and verify Notis archives the context.
Questions about this workflow
What exactly gets archived?
Customer name, company, preferences, issue summary, solutions you tried, and any relevant links or notes from the conversation.
Where does it get archived?
Google Docs, Notion, Airtable, or any system you use for CRM. You configure the destination.
Can I search the archive?
Yes. It's stored in a searchable doc or database so looking up a returning customer is instant.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Agentql. A trigger fires from one place; an action lands in another.
Linear triggers
Agentql actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Usage Details
Tool to retrieve subscription usage details for the current api key, including usage limits and billing period. use after confirming api connection is valid.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Query Data
Tool to query structured data as json from a web page using an agentql query or natural language prompt. use after defining your query or prompt and a url or html.
Comment Received Trigger
Triggered when a comment is received.
Create Remote Browser Session
Tool to create a remote browser session. use when you need to run browser automation on remote infrastructure.
Issue Created Trigger
Triggered when a new issue is created.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Connect any two apps with Notis in the middle.
Linear and Agentql, 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 Agentql.