Workflow Automation not working

[SFS Guwahati]

I have set up a workflow to automate sending birthday wishes from an Excel sheet to WhatsApp. I have a verified Meta Business account, created a new Cloud API setup through https://developers.facebook.com/, and built the complete workflow using Pabbly.com. However, the automation is still not working as expected.

 

[Preeti Paryani]

Hello @SFS Guwahati,

It appears that you are currently using a temporary access token to connect with the WhatsApp Cloud API. We recommend switching to a permanent access token to resolve this issue.

Please refer to the attached tutorial for detailed steps on setting up a connection using a permanent access token.

Let us know if you need any further assistance!

 

[SFS Guwahati]

Hello @SFS Guwahati,

It appears that you are currently using a temporary access token to connect with the WhatsApp Cloud API. We recommend switching to a permanent access token to resolve this issue.

Please refer to the attached tutorial for detailed steps on setting up a connection using a permanent access token.

Let us know if you need any further assistance!

Thank you for the guidance.
I have created a permanent access token from Meta Business Suite, and it is now reflecting on https://developers.facebook.com.
I have also attached a screenshot of the Access Token Debugger tool showing that the token is valid.

However, I tested the setup again, and the message is still not sending.

 

[Preeti Paryani]

Hello @SFS Guwahati,

Could you please provide us with the Workflow URL where you are facing this issue? This will help us investigate the problem more effectively and assist you accordingly.

 

[SFS Guwahati]

Hello Maam,

Thank you for your response.
The workflow URL where I’m facing the issue is mentioned below:

Pabbly

connect.pabbly.com

 

[Preeti Paryani]

Hello @SFS Guwahati,

Upon reviewing your workflow, we noticed that you're still using the same connection that was established on 25th April. As per the error message, the session associated with that connection expired on the same day.

To resolve this, we recommend creating a new connection using the permanent token you've already generated. Once the new connection is established, try sending the template again.

We hope this clarifies the necessary steps. Please proceed with the update and let us know how it goes.

 

[SFS Guwahati]

Hello,

Thank you for your update.

I’ve changed the connection to use the permanent token in the cloned campaign as suggested. However, I’m now encountering a new error:

(#100) The parameter template['components'][0]['type'] is required.

Could you please guide me on how to properly configure the components in the cloned campaign to resolve this?

 

[SFS Guwahati]

While testing the workflow, I noticed that the response received still shows the following data:

"Name": "PORISHMITA GOSWAMI", "Date of Birth": "25/04", "Year of Birth": "1992", "Phone Number": "9706462504"

However, the test input I used was:

Name: Mrinmoy Test, Date of Birth: 30/04, Year of Birth: 1996, Phone Number: 7002423528

It seems like the response is still picking up an older or incorrect row (rowIndex: 137), instead of the one I intended to test with. Could you please help me identify if I’m missing a step, or if there’s an issue with how the trigger is pulling the data?

Thank you!

 

[Preeti Paryani]

Hello @SFS Guwahati,

Would you be available to join us for a quick Google Meet session so that we can assist you more effectively in resolving this issue? Please let us know your convenient time — either between 11:00 AM to 1:00 PM IST or 4:00 PM to 5:00 PM IST.

We look forward to your confirmation.