n8n Automations For Triage And Auto Response

FreightTiger has two n8n workflows configured for Pylon ticket triage. The detailed implementation lives in n8n, so this page only captures the business logic and handoff intent.

Why It Exists

New tickets often need manual cleanup before the support or engineering team can act. The n8n workflows reduce that first-pass effort by identifying the right account, extracting bug context, tagging tickets that need follow-up, and notifying the team in Slack.

Workflow 1: Account Auto-Routing

Business logic:

1. A new Pylon ticket triggers the n8n workflow.
2. The workflow checks the requester email, CC emails, ticket subject, and ticket body.
3. It compares that information with Pylon accounts.
4. If there is one clear account match, it assigns the Pylon ticket to that account.
5. If there is no account match, it tags the ticket for customer/account follow-up.
6. If there are multiple possible matches, it leaves the ticket unassigned for human review.
7. It sends a Slack alert explaining what happened.

Outcome:

• Clear matches are routed automatically.
• No-match tickets are tagged for follow-up.
• Ambiguous tickets are escalated to a human instead of being assigned incorrectly.

Workflow 2: Bug Triage Extraction

Business logic:

1. A bug ticket triggers the n8n workflow.
2. The workflow reads the Pylon ticket content and attachments context.
3. An AI step extracts the key bug information:
   • User persona
   • Background
   • Problem statement
   • KPI impacted
   • Impact
   • Success criteria
   • Supporting data
4. The workflow adds the extracted information as an internal note in Pylon.
5. If critical information is missing, it tags the ticket as needing more information.
6. It sends a Slack alert with the extraction status.

Critical fields currently checked for missing information:

• Background
• Problem statement
• Success criteria

Outcome:

• Support and Engineering get a structured internal note.
• Tickets missing critical information are clearly tagged.
• The team gets a Slack alert instead of manually checking every ticket.

Current Auto-Response Status

The current n8n exports add tags, internal Pylon notes, and Slack alerts. If FreightTiger wants the workflow to send an external reply asking the requester for missing details, that should be enabled and reviewed directly in n8n, starting with internal-user tickets only.

Where To Modify

Modify these workflows directly in n8n:

• Account routing workflow: update account matching rules, ignored domains, follow-up tags, and Slack alert wording.
• Bug triage workflow: update the AI extraction prompt, critical-field checklist, missing-information tag, internal note format, and Slack alert wording.

Keep webhook URLs, Pylon API credentials, Slack webhooks, and model credentials inside n8n credentials or FreightTiger's secret manager. Do not publish them in this documentation.

Handoff Note

Once FreightTiger hosts these n8n workflows and updates Pylon trigger destinations to their own n8n instance, implementation-owned workflows should be disabled to avoid duplicate tags, duplicate notes, or duplicate Slack alerts.