Discord Provider

Provider name: discord

What It Does #

The Discord provider uploads a file through a Discord webhook and returns the attachment URL created by Discord.

For integrators, this mostly matters when util_generate_image needs a final URL that is easy to reuse.

Typical Use Case #

Use the Discord provider when you want generated images to end up on Discord itself rather than staying on the original image provider.

This is useful when:

• you already trust Discord as the place where the bot operates
• you want a Discord CDN URL back
• you want a small trace message attached to the upload for debugging or abuse investigation

What It Usually Needs #

The Discord provider needs a webhook URL.

It can also use optional settings such as:

• whether Discord should wait and return the created message immediately
• an optional thread target attached to that webhook

If the webhook is missing, any tool flow depending on this provider is hidden or blocked until it is configured.

What You Can Configure #

Provider fields:

• webhook_url (required)
• wait (optional)
• thread_id (optional)

Provider selection settings that can point to discord:

• image_uploader
• default_image_uploader
• uploader
• default_uploader

Practical meaning:

• use image_uploader / default_image_uploader when you want generated images to be uploaded to Discord
• use uploader / default_uploader when you want Discord to act as the generic upload fallback

Filename Behavior #

When no explicit filename is provided, this provider normalizes the filename by default from the MIME type.

Examples:

• PNG image -> image.png
• plain text -> text.txt
• JSON file -> file.json

That behavior is especially useful for generated images because the caller does not need to guess a filename manually.

Related Tools #

• util_generate_image

Related Settings #

• webhook_url
• wait
• thread_id
• image_uploader
• default_image_uploader
• uploader
• default_uploader