I’m using a Human In the Loop node to make modifications to data in a CRM platform.
I want to provide the modified values in a form (via Human In The Loop), so the user can manipulate them, and then submit them. However, i’m not finding a way to do this. I can use a placeholder, but then the data isn’t submitted with the form. I’ve tinkered with the custom HTML element, but that doesn’t seem to work.
To be really clear, the user should get a form with several fields, and each field should be pre populated, letting them press submit, or make changes, and then press submit.
I do not have a definitive answer to the question but I try to reason with you and I hope I can help you.
To do what you want, in my opinion, you could save the pre-filled fields in one place (the CRM that you mention, Google Sheet, Airtable, etc.) and then create a human in the loop node to make the flow wait for someone to tell you to continue.
Before this the person edits the saved fields and then starts the flow.
The Human in the Loop therefore works as a step to wait for human intervention.
Let me know if it can work and if it’s clear what I mean.
Thanks. It sounds like you’re recommending I persist the values. I assume you’re then suggesting I wouldn’t use the Gmail Human In The Loop Module like i am now, and use some other mechanism to wait?
I was wondering if there’s some other way to wait for a api call, which I assume is what’s happening in the background with these nodes…
I’m guessing there isn’t a way to simply do this with the form then huh?
As far as I know, the Human in the Loop node does not provide this option at the moment but only an actual approval or rejection of what was done previously.
@Gallo_AIA Can you walk me through what you’re proposing then, maybe with steps and relevant nodes? It’s not clear to me how your suggestion would get implemented.
I’ll tell you my idea but it might not work for your flow but you’ll tell me.
What I was thinking is that you could split your flow into two different flows:
the first one writes on the CRM and you are notified by email when this first flow is completed
After this first phase a person controls the output of the flow, modifies what they want and takes an action to activate the second workflow (the trigger could be anything you want) at this point the second workflow is activated.
I think I’m with you. Persist the values, and build another flow that manages the updates. For example it polls the dB for new entries, once found it sends an email with a custom form. Another webhook is setup to receive that form data and enter it into the CRM. Something like that correct?
I really with those forms were more flexible. I have a feeling there’s lots of people who’d like to do what I’m trying to do.