Bring GREEN-API for WhatsApp into
the flow of work.
A little less busywork with GREEN-API for WhatsApp.
Gather contextDo the workReview & share
Account6 capabilities+
- Get settings
- Get state instance
- Get information about the account
- Logout instance
- Reboot instance
- Set settings
Sending8 capabilities+
- Forward messages
- Send a contact
- Send file by url
- Send interactive buttons
- Send interactive buttons reply
- Send a location
- Send message
- Send poll
Queue2 capabilities+
- Show messages queue
- Clear messages queue
Journal4 capabilities+
- Get chat history
- Get a message
- Get last incoming messages
- Get last outgoing messages
Service10 capabilities+
- Archive a chat
- Check whats app account availability
- Delete a message
- Edit the text message
- Get avatar
- Get contact info
- Get contacts
- Mark chat as read
- Change the settings of disappearing chat messages
- Unarchive a chat
Group8 capabilities+
- Add group participant
- Create a group
- Get group data
- Leave group
- Remove group admin
- Remove group participant
- Set group admin
- Update group name
Status7 capabilities+
- Delete a status
- Get incoming statuses
- Get outgoing statuses
- Get status statistic
- Send a media status
- Send a text status
- Send a voice status
Receiving1 capabilities+
- Download a file
Frequently asked
questions.
What could an Ambacti integration do with GREEN-API for WhatsApp?
The documented operations include Account: Get settings; Account: Get state instance; Account: Get information about the account; Account: Logout instance.
Could I keep a workflow read-only?
For a read-only workflow, limit account permissions to reading data and exclude actions that create, update, or delete records.
Will every action run automatically?
Choose which steps could run on their own and which should pause for review. Changes should follow the permissions and approval rules you set.
Do I need to review actions in GREEN-API for WhatsApp?
Decide which work could run on its own and which steps need your review.