Turn approved document support requests into service requests
Move a clear request into the service catalog process without retyping it by hand.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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).
Why this helps
Approved support needs can stall when someone still has to recreate the request in another system.
- Create a service request from a submitted need.
- Reduce repeated entry for approved requests.
- Keep the request inside Freshservice's catalog process.
Setup
Build it in a few focused steps.
- 1Connect Pdf4me and Freshservice to Notis once in the portal.
- 2Ask Notis to create a Freshservice service request when an approved PDF workflow request reaches its webhook.
- 3Include the intended catalog item in your plain-language instruction; confirm its display ID from the Freshservice catalog beforehand.
- 4Choose an incoming webhook trigger and run-report channel, then test with one approved real example.
Questions about this workflow
What is needed to create the service request?
The Freshservice action requires a catalog item display ID, available from the item's page in Admin > Service Catalog.
Should every incoming request be submitted?
Use a webhook from an approval process or instruct Notis to submit only requests that the incoming details identify as approved.
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.