The flow
Starts it 3Logic 8Service 3
The steps in the order they run, from what starts it.
- 1π New Ticket WebhookWebhookStarts it
- 2π Update Ticket WebhookWebhookStarts it
- 3π£ Linear Issue Updated WebhookWebhookStarts it
- 4πΊοΈ Map Freshdesk Fields to LinearFunctionLogic
- 5π Map Linear to Freshdesk FieldsFunctionLogic
- 6π― Create Linear IssueHttp RequestService
- 7π Check if Freshdesk Ticket ID ExistsIfLogic
- 8β
Check Linear Creation SuccessIfLogic
- 9π« Update Freshdesk TicketHttp RequestService
- 10β οΈ Log Missing Ticket ID ErrorFunctionLogic
- 11π Link Freshdesk with Linear IDHttp RequestService
- 12β Log Linear Creation ErrorFunctionLogic
- 13β
Log Freshdesk Update SuccessFunctionLogic
- 14π Log Linear Creation SuccessFunctionLogic
How it's built
- Starts on
- Another system calling it
- Steps
- 14, with 2 branches
- Size
- Medium: a working afternoon
- Connects to
- Nothing by connector; it calls services over plain HTTP
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on another system calling it.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 14 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Before you run itNothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 14 steps before you point it at anything that matters.