I’ve set a Custom Action based on an Integromat (Make) webhook to send an email to the recipients of the messages generated within the chats in my app.
The information I send to Integromat is the sender’s (logged-in user) and recipient’s (current user) full name, and the recipient’s email. And it’s sent when the sender clicks on the button to send the message.
The email is sent properly when I run the test using the Custom Action menu to test it. But when a message is sent using the app, the scenario (or webhook) in Integromat gets stuck into the queue because the recipient’s full name and email is received as an undefined value.
I’ve already set up an email verification via OTP using a webhook based Custom Action with Integromat. And I’ve tried to find the problem with this but I’ve ran out of idead to solve that.
It might be worthwhile to check that actual data for the last 2 fields (Recipient full name and Recipient email) actually exists / or that magic text entries are set up correctly (it is easy to confuse logged-in user and current user with a mouse movement).
I’ve just made sure that the data exists and that the magic text entries are set up correctly. And everything is correct.
I also guess that regardless of wather the data comes from the logged-in user or the current user, the data should be transfered to Integromat correctly, without receiving undefined data.
Anyway, I’ve made another test and it keeps generating the same problem.
As you can imagine it’s difficult to debug such issues in the forum
Few things you can do to check:
add this custom action at a completely separate screen, no lists, try to pass hardcoded values.
→ if you still receive “underfined”, the problem is with the function
→ if you receive actual data, the problem is with data via magic text.
after that, try to pass magic text values through the same action. You can use “logged-in user”.
→ if all works correct, problem is with the data on the screen.
have a look what’s being actually send to Make. You can see it in browser console, network tab. When you press a button which calls this custom action, there will be a call to custom actions backend server, and you can see the payload there. If the payload is correct, then there is something on Make side.
Check for commas or double quotes in the payload - this sometimes may cause issues.
Try recreating the custom action from scratch and see if it works or not.