Workflow not working

[robbiereyes]

Your Workflow URL

https://connect.pabbly.com/workflow/mapping/IjU3NmMwNTY4MDYzMDA0MzA1MjY4NTUzZCI_3D_pc

Consent to Access & Modify

I authorize Pabbly Support to log in to my account and make changes to the specified workflow for troubleshooting.

This workflow was working fine, until recently. I did not make any changes in the meantime.

The result should be an email sent by Gmail with screenshots attached. For some reason I'm not receiving the email. If I test I do receive the email but without attachements,

Hope you can help!

 

[Preeti Paryani]

Hello @robbiereyes,

Thanks for reaching out.

Upon checking, it appears that the workflow was last triggered on 15 December. Currently, under the workflow builder, the trigger is waiting for a response, and no new webhook response has been captured since then, which is likely causing the issue.

We recommend triggering the event again from Hexomatic and checking whether the current workflow captures the response in the builder. If it does not, please try setting up a new workflow for the same use case and test it again.

Let us know how it goes, and we’ll be happy to assist further if needed.

 

[robbiereyes]

The trigger is working. I think the issue is in the screenshot. How can I separate the URL's?

 

[Preeti Paryani]

Hello @robbiereyes,

I have added a Text Formatter step at Step 6 in your workflow to help you separate the URLs correctly.

Please refer to the attached screenshot for a clear understanding of how it works.

 

[robbiereyes]

Thank you so much. When I now test the first step I get this:

How do I resolve this?

 

[Preeti Paryani]

Hi,

Upon checking your workflow, it seems the trigger has been waiting for a webhook response for a long time, and the response captured earlier does not contain any array data. It is only capturing a single “Data” field with a string value (json_stringify_data).

Due to this, the Line Itemizer step cannot process it correctly because it requires an array input.

To resolve this, please try the following:

1. Trigger the event again from Hexomatic and re-capture the webhook response.
2. If it still captures only the “Data” in array format, you may map it further, if not please try setting up a new workflow and see if you're able to capture the correct response there.
3. In the Line Itemizer step, ensure you are mapping the actual array field, as mentioned in the help text (not the string value).

Once the trigger captures the array properly, the Line Itemizer will work as expected.

 

[robbiereyes]

Thank you for your help. I set up a new workflow: https://connect.pabbly.com/workflow/mapping/IjU3NjcwNTZjMDYzNTA0Mzc1MjZkNTUzMDUxMzYi_pc

The output I get now is:

How do I use the text formatter to grab this .png file?

 

[Preeti Paryani]

Hey @robbiereyes,

You can extract the PNG file using the Extract Pattern action under the Text Formatter. We have already added this action to your workflow for your reference.

Please review it and let us know if you need any further assistance.

 

[robbiereyes]

Thank you so much!

When trying to send the URL as attachement with Gmail I get this error:

How can i resolve this?

 

[Preeti Paryani]

Hello @robbiereyes,

Thanks for reaching out to us.

Regarding the attachment issue, please note that the extracted URL alone does not remain a valid or downloadable URL. We recommend using the complete URL as received from the trigger, as that is the publicly accessible link and can be fetched correctly.

Additionally, for the Gmail action, it appears there may be an issue with the Gmail connection. The sender email address is not auto-populating, which usually indicates that the Gmail connection has either expired or is not connected to the correct account.

We recommend reconnecting Gmail and ensuring you connect the same Gmail account from which you intend to send the emails. Once reconnected, please test the action again.

Let us know if the issue persists after this, and we’ll be happy to assist further.

 

[robbiereyes]

I've reconnected my Gmail.

I do not fully understand: We recommend using the complete URL as received from the trigger, as that is the publicly accessible link and can be fetched correctly.

Which is the original URL?