FRESHSERVICE n8n INTEGRATION: AUTOMATE FRESHSERVICE WITH N8N

This action allows you to modify an existing support ticket in Freshservice. Whether you need to change the status, reassign to a different agent, update the priority, or add custom field values, this action handles it all.

Key parameters: Credential to connect with (required dropdown), Resource set to "Ticket" (required), Operation set to "Update" (required), Ticket ID (required text input), and Update Fields where you can add specific properties to modify—status, priority, agent assignment, custom fields, etc.

Use cases: Automatically escalate tickets that have been open for more than 24 hours, update ticket status when a related change request is approved, or reassign tickets when an agent goes on vacation.

This action retrieves multiple tickets from your Freshservice instance, perfect for bulk operations, reporting, or syncing ticket data with external systems.

Key parameters: Credential to connect with (required), Resource set to "Ticket" (required), Operation set to "Get Many" (required), Return All toggle to fetch all tickets (optional), Limit to set maximum number of tickets to retrieve (numeric input, default 50), and Filters to add filtering criteria.

Use cases: Export all open tickets to a Google Sheet for team review, fetch tickets assigned to a specific agent for workload analysis, or retrieve high-priority tickets for executive dashboards.

This action retrieves detailed information about a single ticket using its unique identifier. Perfect for workflows that need to check ticket status or pull ticket data for processing.

Key parameters: Credential to connect with (required), Resource set to "Ticket" (required), Operation set to "Get" (required), and Ticket ID (required text input).

Use cases: Check if a ticket is resolved before sending a follow-up email, retrieve ticket details to include in a Slack notification, or validate ticket existence before performing update operations.

This action permanently removes a ticket from your Freshservice instance. Use with caution—this operation cannot be undone.

Key parameters: Credential to connect with (required), Resource set to "Ticket" (required), Operation set to "Delete" (required), and Ticket ID (required text input).

Use cases: Clean up test tickets created during workflow development, remove duplicate tickets automatically detected by your system, or archive old resolved tickets beyond your retention policy.

This action creates a new support ticket in Freshservice with all the essential details—requester email, subject, description, priority, and status.

Key parameters: Credential to connect with (required), Resource set to "Ticket" (required), Operation set to "Create" (required), Email (required text input), Subject (optional but recommended), Description (optional), Priority dropdown (Low, Medium, High, Urgent), Status dropdown (Open, Pending, Resolved), and Additional Fields for custom properties.

Use cases: Auto-create tickets from website contact forms, generate tickets when monitoring systems detect anomalies, or create onboarding tickets when new employees are added to BambooHR or your HR system.

This action modifies software records in your Freshservice asset management module. Keep your software inventory up-to-date by automating version updates, license changes, or metadata modifications.

Key parameters: Credential to connect with (required), Resource set to "Software" (required), Operation set to "Update" (required), Software ID (required text input), and Update Fields where you can add properties to modify.

Use cases: Update software version numbers when new releases are deployed, modify license counts when procurement completes purchases, or sync software metadata with your procurement system.

This action retrieves multiple software records from your Freshservice instance, useful for inventory audits, license compliance checks, or integration with procurement systems.

Key parameters: Credential to connect with (required), Resource set to "Software" (required), Operation set to "Get Many" (required), Return All toggle (optional), and Limit (default 50).

Use cases: Export software inventory for compliance auditing, sync software list with a license management tool, or generate reports on installed applications across your organization.

This action retrieves detailed information about a single software entry using its unique identifier.

Key parameters: Credential to connect with (required), Resource set to "Software" (required), Operation set to "Get" (required), and Software ID (required text input).

Use cases: Verify software details before triggering an update workflow, fetch software metadata to include in approval requests, or check software status as part of a deployment pipeline.

This action removes a software record from your Freshservice asset management.

Key parameters: Credential to connect with (required), Resource set to "Software" (required), Operation set to "Delete" (required), and Software ID (required text input).

Use cases: Remove deprecated software from inventory automatically, clean up test entries created during integration testing, or archive software no longer in use.

This action creates a new software entry in your Freshservice asset management with details like application type, name, and additional properties.

Key parameters: Credential to connect with (required), Resource set to "Software" (required), Operation set to "Create" (required), Application Type dropdown (Desktop, SaaS, etc.), Name (required text input), and Additional Fields for custom properties.

Use cases: Auto-register new software when procurement approves purchases, add software entries when detected by discovery tools, or create software records from a spreadsheet import workflow.

This action creates a new agent in Freshservice to handle tickets and support requests.

Key parameters: Credential to connect with (required), Resource set to "Agent" (required), Operation set to "Create" (required), and Additional Fields to add email, name, roles, groups, etc.

Use cases: Auto-create agents when new IT staff are hired, provision agents from HR system integrations, or set up temporary agents for contractors.