Problems with Freshdesk Modules that have attachments fields

Hello,

I am using the Freshdesk Create a Ticket Module in one of my scenarios (although this issue applies to all Freshdesk modules that have attachments fields)

The module works without throwing any errors but Freshdesk have advised that the way the data is being sent to them is incorrect.

The module has an “attachments” field where we are to add any attachments to the payload sent to Freshdesk. This fields stores an array of the attachments and the field name in attachments.

Freshdesk have stated in their documentation that anytime the payload is sent to them to create a ticket, if the payload has multiple attachments field, then the content type must the multipart/form-data . This is because the application/json content type can only accommodate one attachment.

When Make.com sends over the data, instead of doing the above, they seem to
-Send the payload in json format without the attachments field to Freshdesk’s CREATE ticket endpoint
-Then send each attachment to Freshdesk’s UPDATE ticket endpoint.

The end result of this is that the attachments are not present when the ticket is created in Freshdesk. Instead, they are created a few seconds later. The problem with that is that there are some emails that go out immediately the ticket is created and these emails are missing the attachments since they are not present in the payload sent to Freshdesk to create the ticket

Freshdesk is a bit confused as to why Make.com is sending data to them in this way, when everything can just be sent to the create a ticket endpoint including the attachments.

Can someone from within Make assist? Please note that this also applies to all Freshdesk Modules in Make that have an attachments field (e.g Send An Outbound Email, Create a Note, Create a Reply etc)

Thanks.
Mo

Welcome to the Make community!

For technical issues or bugs like this, directly contacting support can often lead to a faster resolution. They have access to your specific account details, scenario and scenario logs, server-side logs, and internal tools and resources, which allows them to investigate more thoroughly than what you have access to. Additionally, sharing sensitive information about your account or scenario might not be suitable for an open forum discussion.

You can open a new ticket here, or if you are unable to login for some reason, you can create another new free account to access the ticketing system (which is only available to logged-in users). After submitting a new ticket, you will receive an automatic confirmation email with the subject “Ticket Created” in the subject. If you do not receive this, try sending the ticket again.

If you manage to get your issue resolved with support, we’d still love to hear about it! Sharing your solution on the forum can help others facing similar problems.

Hope this helps! Let me know if there are any further questions or issues.

@samliew

P.S.: Investing some effort into the Make Academy will save you lots of time and frustration using Make.

Thanks Samliew,

I had raised a ticket as well although no resolution yet.

Mo