To read it back, you're saying that you want to have a webhook triggered for document versions, but only if the document is on a project where a specific custom form is attached? If so, then I would add a custom form to the document, and on that form have a calculated field that maps in your filter ...

To make sure I understand, you're saying you have a router with two branches coming off of it, and then you want to bring the two branches back together? If so, what I do is at the end of each of those branches, put a "Set multiple variables" module, and map whatever values you want to pass to your ...

Sometimes you have to run it once for Fusion to pick up what available options are. Sometimes even that doesn't work, in which case you can create a set multiple variables module, map your csv fields into that, and then pick up the variables with your aggregator.

You have to select which fields to pass thru, did you do that?

As an alternative approach, you could place an array aggregator right after the parse CSV, and group it by whatever key you need to ensure is only processed once.

It's fairly straight forward.1. Create a webhook that triggers on project creation, and filter by convertedOpTaskEntryDate != blank, as well as any other filter you'd like2. Update project name

So to make sure I understand, you're saying when a request is converted into a project, you want the project name to change to something like {Project Reference Number} {Original Project Name}? If so, I've done similar things previously, yes.

Fair enough, I was hoping against hope there would be some other way.

No, the UID and reference number both are inviolate, for all objects. As long as you are working with the same object, both of those values will always be the same.

That's correct. In the API, the field is called "ID".