Trigger workflow on database event

[thomtrp]

• Add global listener on database event
• Fetch event listener associated
• Trigger associated workflow

Also updated the runner so it expects the input to be in the payload rather than the trigger

[greptile-apps]

PR Summary

This pull request introduces a global listener for database events to trigger associated workflows, along with updates to the workflow runner to handle input in the payload.

• Module Renaming: packages/twenty-server/src/engine/core-modules/workflow/core-workflow-trigger.module.ts renamed to WorkflowTriggerCoreModule for better organization.
• New Input Type: Added packages/twenty-server/src/engine/core-modules/workflow/dtos/workflow-input.dto.ts to handle JSON payloads for workflow triggers.
• Listener Addition: Introduced packages/twenty-server/src/modules/workflow/workflow-trigger/listeners/database-event-trigger.listener.ts to dynamically trigger workflows based on database events.
• Job Handling: Added packages/twenty-server/src/modules/workflow/workflow-trigger/jobs/workflow-event-trigger.job.ts to manage workflow event triggers via message queues.
• Module Integration: Updated packages/twenty-server/src/modules/workflow/workflow.module.ts to include WorkflowTriggerModule, ensuring seamless integration of the new event-triggering functionality.

_{15 file(s) reviewed, 32 comment(s)
Edit PR Review Bot Settings}

[martmull]

I think we should be consistent between those handle function parameters and the runWorkflowparameters. Lets use the workflowId in runWorkflow then. Also, we should update the workflowCommonService.getWorkflowVersion so that we don't need twentyORMGlobalManager service here
Then the runWorkflow method can also use the updated version of workflowCommonService.getWorkflowVersion

[thomtrp]

@martmull agreed with the input update. But thinking again about the endpoint, I think this is the version we want to run. This endpoint will be used to test versions. I rename it to be consistent. Happy to discuss it if you disagree!

[martmull]

think you can move that in workflow-common.service.ts in a getEventListeners method

[thomtrp]

This is the only place where we fetch eventListeners and not sure we will have others. I prefer put in common functions that will be used in several places, across sub-modules. Wdyt?

[martmull]

ok

[martmull]

Some comments