שִׂיג ושִׂיח | cig.chatInstall

Summary

Send ordered content to a Cig.chat subscriber, optionally with actions, quick replies, and a flow destination. The request can be sent as the bot or as a human agent.

Inputs

• Subscriber NS (required) — Subscriber identifier to receive the content.
• Send as Agent — Send as a human agent when enabled; otherwise use the API's bot default.
• Messages — Add message bubbles in send order. Choose Text, Image, Audio, Video, File, or Cards; enter Text as the body or media caption, and a public Media URL for media types. Cards need an elements array not exposed here; use the Universal module for cards.
• Actions — Optionally run actions alongside the message: add or remove a tag, set a field value, or unset a field value. Tag actions use Tag; field actions use Field name, and setting a value also uses Field value. The field key names are undocumented, so verify them with a test send.
• Quick Replies — Optionally add tappable buttons beneath the message. Each requires a caption and a target: a node NS, full URL, or dynamic block callback name, depending on the selected type.
• Go to Node — Optionally specify the node name or node_ns where the flow continues after this content.
• Request Options — Configure batching, SSL certificate validation, an HTTP proxy, or request timeout.

Output shape

A single API response for the send request.

The provided source pack omits function bodies, so it does not establish the response fields or confirm runtime request behavior beyond the declared routing. Messages, actions, and quick replies are configured as lists; the UI describes messages as sent in order.

Links

• n8n community nodes installation guide