Research

Key pain points

  • High effort and duplication: Workflows like connector calls or data syncs were being duplicated across apps

  • Lack of real-time triggers: Users couldn’t react to key system events like table updates, machine alarms, or operator actions

  • Delayed or missed responses: No reliable way to send alerts or escalate based on thresholds or downtime

  • Non-value-added time: Engineers spent time maintaining logic inside apps that didn’t need a UI

  • Scalability issues: Critical business logic couldn’t be easily reused or managed centrally

Solution

  • Event-based triggers: Listen to system events like table updates, machine states, app completions, timers, or insights

  • Run ‘headlessly’ in the cloud: Automations execute without user interaction or interface

  • Drag-and-drop builder: Create logic visually—no need for code or traditional scripting

  • Native access to Tulip resources: Read/write to tables, run connector functions, send alerts (email/SMS), and more

  • Modular and reusable: Automations can be triggered from apps or other automations for advanced orchestration

  • Audit-friendly: Full transparency into what ran, when, and why


Impact

The customizable workflows and streamlined interface of Automations became a key selling point in securing new deals and 2 years later, the feature:

  • Powers 300+ customers executing 40 million tasks on average per month.

  • Achieved 76% user retention after launch—showing the automation feature became a habitual part of the workflow.


Back