Actions64
- Instance Actions
- Message Actions
- Group Actions
- Chat Actions
- Profile Actions
- Event Actions
- Integration Actions
Integration → Aysali Bot
AI-generatedSummary
Aysali Bot Integration Operation
Inputs
- action (required) — Choose an action: createEvolutionBot, findEvolutionBot, updateEvolutionBot, deleteEvolutionBot, fetchSessionsEvolutionBot, or changeStatusEvolutionBot
- instanceName (required) — Instance name that will send the message
- apiUrl (required) — Aysali Bot API URL
- apiKeyBot (required) — Aysali Bot API key
- triggerType (required) — Keyword or All
- triggerOperator (required) — Contains, Equals, Starts With, Ends With, or Regex
- triggerValue (required) — Word, phrase, or regex used as the trigger
- expire (required) — Minutes without replies before the bot is disabled
- keywordFinish (required) — Word or phrase used to close the bot
- delayMessage (required) — Bot message delay in milliseconds
- unknownMessage (required) — Word or phrase used to close the bot
- listeningFromMe (required) — Whether to listen to messages sent by me
- stopBotFromMe (required) — Whether to pause bot when I send a message
- keepOpen (required) — Whether to keep bot session open
- debounceTime (required) — Debounce time in seconds
- remoteJid (required) — Recipient remote JID
- status (required) — Session status: opened, paused, or closed
- ignoreJids (required) — List of JIDs ignored by the bot
Output shape
depends on action
Returns Aysali Bot data, session list, or status update based on chosen action
Examples
Example 1: Create a new Evolution Bot
Set action to createEvolutionBot, provide instanceName, apiUrl, apiKeyBot, triggerType, triggerOperator, triggerValue, expire, keywordFinish, delayMessage, unknownMessage, listeningFromMe, stopBotFromMe, keepOpen, debounceTime, remoteJid, and status. The bot will be configured with these parameters and start listening for the trigger.
Example 2: Change session status
Set action to changeStatusEvolutionBot, provide remoteJid and status (opened, paused, or closed). This will change the status of the specified bot session.
Example 3: Fetch bot sessions
Set action to fetchSessionsEvolutionBot to list all bot sessions. No additional parameters required beyond the instance configuration.