Make document incident review a weekly habit
Gather the week's relevant tickets into one review instead of searching whenever a problem resurfaces.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List Freshservice Tickets
Tool to list all tickets in Freshservice with optional filtering and pagination. Use when you need to retrieve ticket IDs or search for tickets. By default only tickets created within the past 30 days are returned; use updated_since for older tickets.
Why this helps
Document incidents spread across the week can be hard to reconstruct during a later review.
- See related incidents together.
- Make recurring issues easier to notice.
- Spend less time reconstructing the week's work.
Setup
Build it in a few focused steps.
- 1Connect Pdf4me and Freshservice to Notis once in the portal.
- 2Ask Notis to list recent Freshservice tickets weekly and summarize those connected to document processing.
- 3Use one plain-language prompt to describe the review summary you want.
- 4Select a weekly recurring trigger and a run-report channel, then check the first real weekly summary.
Questions about this workflow
Can this identify patterns across tickets?
Notis can summarize listed ticket details according to your instruction, within the information available from the list action.
Does the schedule create new tickets?
No. It lists tickets to prepare a review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Pdf4me to Freshservice. A trigger fires from one place; an action lands in another.
Pdf4me triggers
Freshservice actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Bulk Update Tickets
Tool to bulk update multiple Freshservice tickets by sequential update calls. Use when you need to update fields across many tickets in absence of a native bulk API.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Service Request
Create a service request for a catalog item in Freshservice using the v2 API. The catalog item display_id can be found in Admin > Service Catalog by clicking on an item and checking the URL (e.g., /service_catalog/items/1 means display_id=1).
Create Ticket
Tool to create a new ticket. Use when you need to log an incident or service request.
Delete Release
Tool to delete a release from Freshservice. Use when you need to permanently remove a release from the system. This action is irreversible — the release cannot be recovered once deleted.
Delete Solution Article
Tool to delete a solution article from the knowledge base by its ID. This action is irreversible — the article cannot be recovered once deleted. Use this action when you need to permanently remove a solution article from Freshservice.
Delete Solution Category
Tool to delete a solution category in Freshservice. Use this action when you need to remove a solution category that is no longer needed. This action is irreversible — the category cannot be recovered once deleted.
Get Problem Form Fields by Workspace
Tool to list problem form fields. Use when you need to retrieve the form fields available for problems in a specific workspace.
List Release Form Fields
Tool to list release form fields metadata. Use when you need to fetch release field definitions before building or validating release forms.
Connect any two apps with Notis in the middle.
Pdf4me and Freshservice, 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 Freshservice.