Currently, payloads vary across platforms and scenarios.
For example, reactions are sent as a different event, with both received and sent reactions using a reaction.received event.
This makes building automations downstream cumbersome, especially since all platform events are sent to the same webhook
For instance, I’m attaching a screenshot of Make.com logic for a logging header in our CRM (what happened and who did it), covering different WhatsApp scenarios. More scenarios will likely surface in the future, and I haven’t even started testing Facebook yet.
I suggest creating a unified object such as:
Platform: WhatsApp/Facebook/Instagram;
Type: Text/Audio/Contact/File/Image/Reaction;
Direction: Sent/Received;
Action: Added/Removed (for reactions, for example);
Participant Name: The other party. This field exists but is sometimes missing, even though it can be inferred from other fields like Sender Name.
This would make creating automations much easier and simplify the onboarding process.
Thanks for a great platform.

Please authenticate to join the conversation.
In Review
Feature Request
28 days ago

asafm7
Get notified by email when there are changes.
In Review
Feature Request
28 days ago

asafm7
Get notified by email when there are changes.