Z-API WhatsApp × AmbactiBring Z-API WhatsApp into
the flow of work.
A little less busywork with Z-API WhatsApp.
Gather contextDo the workReview & share
API1 capabilities+
- Make an API call
Generic request to any Z-API endpoint (escape hatch)
Message15 capabilities+
- Delete message
- Read a message
- Reply to a message
- Send a button list
- Send a contact
- Send a document
- Send a link
- Send a location
- Send an image
- Send an audio
- Send an option list
- Send a PIX button
- Send a sticker
- Send text message
- Send a video
Group13 capabilities+
- Promote to admin
- Add participant
- Create group
- Get invitation metadata
- Get group metadata
- Leave group
- Demote admin
- Remove participant
- Send invite link
- Update description
- Update name
- Update photo
- Update settings
Chat4 capabilities+
- Archive chat
- Delete chat
- List chats
- Pin chat
Contact4 capabilities+
- Check phone exists
- Get contact metadata
- Get profile picture
- List contacts
Product5 capabilities+
- Upsert product
- Delete product
- Get product
- Get products by phone
- List products
Message Queue2 capabilities+
- Delete queue message
- Get queue messages
Status2 capabilities+
- Post image to status
- Post text to status
Instance5 capabilities+
- Disconnect phone
- Get device data
- Get qr code bytes
- Get qr code image
- Get phone code
Frequently asked
questions.
What could an Ambacti integration do with Z-API WhatsApp?
The documented operations include API: Make an API call; Message: Delete message; Message: Read a message; Message: Reply to a message.
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 Z-API WhatsApp?
Decide which work could run on its own and which steps need your review.