Is it possible to specify whether an action can come after the other in the workflow builder?

[Abdssamie]

I really like the flexibility of the Inngest workflow builder UI — it makes building workflows easy. However, I ran into a challenge: not every action can logically follow another in my workflows, and currently there doesn’t seem to be a built-in way to enforce or guide action compatibility.

!! This example was just generated by ai and is just for demonstration
Suppose you have these two actions:

“Wait for Event” — waits for a webhook or incoming event.

Output: { eventData: any }

“Add Numbers” — takes { a: number, b: number } as input and returns their sum.

It doesn’t make sense to place “Add Numbers” immediately after “Wait for Event”, because the event output { eventData: any } doesn’t match the expected inputs { a, b }. Currently, the workflow builder allows this connection, which would fail at runtime.

Could you advise on best practices or features to handle this type of situation if it is possible in the current version of the sdk? if not I guess I would have to make my own custom workflow builder?

[Abdssamie]

So what I can tell is that inngest workflows are not generic pipelines for data transformations but are actually tied my application's domain and events. If this is correct, I guess this solves the issue above