# How are you handling Fin workflows when the native builder feels too limited?

Fin has been great for flexibility (placing the messenger anywhere), analytics, and building custom reports and dashboards. The shared inbox setup also helps keep Messenger and email tickets together, and the AI agent can stay current by refetching web sources. But the workflow builder feels stiff: no webhook triggers, only one trigger per workflow, no drag-and-drop reordering, and no parallel branches, which pushes us to use tools like n8n or Zapier and then trigger Fin workflows. How are others working around these workflow limitations, and what would you want Fin to add first?

##### Post Metadata
- Posted at: about 1 month ago
- Author title: Customer Support Manager
- Net upvotes: 1



## Related Product
[Fin](https://www.g2.com/products/fin/reviews)

## Related Category
[AI Customer Support Agents](https://www.g2.com/categories/ai-customer-support-agents)

## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4