Qiscus OmnichannelInstall

Summary

Send a message to a Qiscus Omnichannel room as the app’s admin bot. Choose a text, attachment, buttons, carousel, quick reply, or sticker message and provide the fields shown for that type.

Inputs

• Type (required) — Message format: Text (default), Attachment, Buttons, Carousel, Quick Reply, or Sticker.
• Room ID (required) — ID of the room to send the message to.
• Message (required) — Message text used for Text, Attachment, Buttons, Carousel, and Quick Reply. The implementation reads this field for those types; for buttons it also sends Body Text as the button message text.
• Attachment URL (required) — URL of the attachment; shown for Attachment messages.
• Caption (required) — Caption for the attachment; shown for Attachment messages.
• Body Text (required) — Text displayed above the buttons; used for Buttons messages.
• Buttons — For Buttons messages, add buttons with a label, type (Postback or Link), and URL. Postback buttons also support a GET or POST method, defaulting to GET.
• Cards — For Carousel messages, add cards with a title, image URL, description, default action URL, optional default action method and postback text, and optional buttons. Each card's default action is sent as a postback.
• Quick Replies — For Quick Reply messages, add replies with a user-facing label and postback data.
• Sticker Version (required) — For Sticker messages, choose V1 or V2 (default). V1 formats the sticker URL into a text message; V2 sends the URL as the sticker payload.
• Sticker URL (required) — URL of the sticker image, typically a .webp file.

Output shape

One or more n8n items containing the Qiscus API response as JSON.

The operation sends a POST request to the app's bot endpoint using the configured Qiscus credentials and an app admin sender address. The API response is wrapped as JSON output; with Continue On Fail enabled, an error item is returned for a failed input item.

Links

• n8n community nodes installation guide