Workflows are not working properly

[brainpower]

Your Task History ID

1- IjU3NjUwNTZlMDYzMzA0MzY1MjY4NTUzYzUxMzE1MTZiNTQzMzBmMzAi_pc IjU3NjUwNTZlMDYzMzA0MzY1MjY4NTUzYzUxMzE1MTZiNTQzMzBmMzAi_pc

Hi, Happy Thursday!

I'm encountering issues with Pabbly Connect while setting up automated client onboarding and offboarding workflows.

During testing of the client onboarding workflow a few days ago:

* Instead of sending one email, the system sent three.
* Instead of creating one task from a template on ClickUp, it created three.
* I've tried disconnecting and reconnecting the apps, but the problem persists.

I encountered similar issues today while testing the client offboarding workflow:

* The system created three tasks from a ClickUp template instead of one.
* The email was sent to the CC instead of the intended recipient.

Both workflows have consumed 91 tasks, all of which are tests, not live tasks.

Could you please advise on how to resolve these issues?

Thank you!
Diana

 

[Preeti Paryani]

Hello @brainpower,

The errors you're experiencing may be due to multiple clicks on the "Save and Send Test Request" button, which could have led to Multiple triggers(data duplication). For more details, please refer to the attached image.

We recommend setting up the workflow again and re-establishing the connection with the trigger step. Be sure to click the "Save and Send Test Request" button once. If you want to capture another response use the "Recapture Webhook Response" button. Please test this setup to see if it resolves the issue.

 

[brainpower]

Hello @brainpower,

The errors you're experiencing may be due to multiple clicks on the "Save and Send Test Request" button, which could have led to Multiple triggers(data duplication). For more details, please refer to the attached image.

We recommend setting up the workflow again and re-establishing the connection with the trigger step. Be sure to click the "Save and Send Test Request" button once. If you want to capture another response use the "Recapture Webhook Response" button. Please test this setup to see if it resolves the issue.

Hello Preeti:
It didn't work. I tried deleting the workflow and starting over, and I got this:

 

[ArshilAhmad]

Could you please share the newly created Workflow URL?

 

[brainpower]

Could you please share the newly created Workflow URL?

Sure! Are these:

Client Onboarding: https://connect.pabbly.com/v2/app/w...MDG1fSwEFA1VTIAcdU39dXlIoB0pRKg1UXG8BXwMrB2Y#

Client Offboarding:

Pabbly Connect

connect.pabbly.com

Thank you!

 

[ArshilAhmad]

The Client Offboarding workflow does not have any trigger or action steps for us to review.

Pabbly

connect.pabbly.com

As for the Client Onboarding workflow, it looks like you have selected multiple webhook events during the Plutio trigger step setup. Please reconfigure your trigger step and ensure that you select only one event during the webhook setup, unselecting all other events as shown in the video.

Pabbly

connect.pabbly.com

 

[brainpower]

The Client Offboarding workflow does not have any trigger or action steps for us to review.

Pabbly

connect.pabbly.com

As for the Client Onboarding workflow, it looks like you have selected multiple webhook events during the Plutio trigger step setup. Please reconfigure your trigger step and ensure that you select only one event during the webhook setup, unselecting all other events as shown in the video.

Pabbly

connect.pabbly.com

Thanks for your answer. For the client offboarding, I had to delete that workflow.

Now, I'm still trying to set up the client onboarding, and I'm still struggling. What I need to do is get a trigger in Pabbly when an invoice is paid in Plutio. I also need to get the client's name from Plutio for the next step in the workflow, which is to send an email with the information of the new client.

 

[Preeti Paryani]

Hello @brainpower,

The trigger you are using is a descriptive webhook-based trigger(refer to the attached image) due to that the responses sent by the Trigger application aren't in our control. Regarding any difficulties faced with the data not getting received from descriptive webhook-based triggers, we recommend you contact their team.