Actions90
- Sessions Actions
- Messages - Sending Actions
- Chats Actions
- Messages - Actions Actions
- Groups Actions
- List Groups
- Group Info
- Get Invite Link
- Revoke Invite Link
- Join via Link
- Preview via Link
- Create Group
- Delete Group
- Update Group Description
- Toggle Announcement Mode
- List Participants
- Add Participants
- Remove Participants
- Demote Participants
- Approve Join Request
- Reject Join Request
- List Join Requests
- Get Group Picture
- Set Group Picture
- Delete Group Picture
- Leave Group
- Update Group Name
- Lock Group Edits
- Promote Participants
- Profile Actions
- Server Actions
- Miscellaneous Actions
Overview
This node operation retrieves profile information from a specified WhatsApp session using the WARest WhatsApp REST API. It is useful for obtaining details about the user's WhatsApp profile, such as name, status, and other profile-related data. This can be applied in scenarios where automation workflows need to access or display WhatsApp profile information for monitoring or integration purposes.
Use Case Examples
- Retrieve the profile info of a specific WhatsApp session to display user details in a dashboard.
- Use the profile info to verify the current status or name of the WhatsApp account in an automated process.
Properties
| Name | Meaning |
|---|---|
| Session | Identifier of the WhatsApp session from which to get the profile info. It can be selected from a list of available sessions or entered manually. |
Output
JSON
json- The JSON object containing the profile information retrieved from the WhatsApp session.
Dependencies
- Requires an API key credential for the WARest WhatsApp REST API and the base URL of the API server.
Troubleshooting
- Ensure the session ID is valid and the session is active; otherwise, the API call to get profile info will fail.
- If the node throws an error stating the operation is not implemented, verify that the resource is set to 'Profile' and the operation to 'Get Profile Info'.
- Check that the API credentials (API key and base URL) are correctly configured and accessible by the node.