We’re building out our first Workflow using Pipefy and alongside this are using Make (an integration tool, akin to ZAPIER) to process data and keep in sync with our other systems.
All very straightforward except when it comes to the challenge of ensuring that the integration engine keeps in step with events on Pipefy.
I’ve developed a solution for this but I want to know whether anyone has a better approach. My solution is as follows;
Whenever a Card is moved, we want the Make integration engine to process data. A webhook is setup accordingly. However, we need to ensure that;
- if the Make integration fails for whatever reason, then any further processing on Make is halted until the issue is resolved.
- if the Webhook fails to fire (it happens!), then any processing of subsequent Phase changes on Make is halted
- a warning message appears on the Pipefy Stage if any of the above conditions have occurred
Ignoring the warning message, then this is the solution I’ve come up with;
1. the Pipefy Pipe has a 'hidden' field on the Start Form 'hidden_process_moved_card_request_placed_for_make_on_phase_id'.
2. Whenever a Card is moved to a Phase, an on-app automation checks the value of this field and if blank, updates the field value to the ID of the current Phase, otherwise if not blank (then the on-app automation does nothing
3. a Pipefy field validation hides all fields on all Phases if the value of this field is not blank (this prevents a user changing data states whilst the Make call is outstanding)
4. A Make Scenario executes whenever a card is moved (via webhook). It first checks to see if the value of the hidden field 'hidden_process_moved_card_request_placed_for_make_on_phase_id' = current Phase ID (the latter passed in the webhook). If these values are the same, then the webhook is processed, otherwise it is abandoned.
Can anyone come up with a simpler solution?
Best answer by mark-theotcentreView original