Flow reference: Plugins
Ticket Transcript
Save the channel's messages (up to 1000) as an HTML transcript and send it to a channel (Tickets Pro plugin).
Save the channel's messages (up to 1000) as an HTML transcript and send it to a channel (Tickets Pro plugin).
When and how to use it
Connect the input from the preceding step on the path that should perform this operation.
Fill the fields with data available in the trigger's context.
Connect the needed outputs; an unconnected path cannot run later blocks.
Configuration fields
Ticket channel — channel
Choose the channel this block targets or filters. Use its Discord ID or a supported channel variable. Check channel overrides for the bot.
Input: Text.
Format example, not a ready value for your server:
{channel}.Default:
{channel}.Send the transcript to — sendTo
Channel receiving the transcript file. Choose a restricted log channel if the transcript contains private support messages.
Input: Text.
Default:
{env.TICKET_LOG_CHANNEL}.Title (optional) — title
Title displayed for the form, transcript or message. Keep it understandable and separate from internal identifiers.
Input: Text with variable suggestions.
Default: ``.
Outputs and next steps
out: Continue to the next step.failed: The operation failed; provide a safe error response.Test and troubleshoot
Install the corresponding plugin and configure its required accounts, channels and secrets. Test an API read before a write operation. An external-service error is not a reason to recreate the whole bot.
Save, validate and publish. Perform one real test and read the first relevant log error. [Testing](/docs/flow-testing) · [Variables](/docs/flow-variables) · [Permissions](/docs/flow-permissions).
Save, validate and publish. Perform one real test and read the first relevant log error. [Testing](/docs/flow-testing) · [Variables](/docs/flow-variables) · [Permissions](/docs/flow-permissions).