Skip to main content

Discord Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow, DB-CDC, Spark ETL, or Replication data flow that sends data to a Discord location.
discord.png

Discord

Create a Discord Destination​

  1. Click the + icon on the Nexset that will be sent to the Discord destination, and select the Send to Destination option from the menu.

  2. Select the Discord connector from the list of available destination connectors. Then, select the credential that will be used to connect to the Discord bot, and click Next; or, create a new Discord credential for use in this flow.

  3. In Nexla, Discord destinations can be created using pre-built endpoint templates, which expedite destination setup for common Discord endpoints. Each template is designed specifically for the corresponding Discord endpoint, making destination configuration easy and efficient.
    • To configure this destination using a template, follow the instructions in Configure Using a Template.

    Discord destinations can also be configured manually, allowing you to send data to Discord endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Discord endpoints. Each template is designed specifically for the corresponding Discord endpoint, making destination setup easy and efficient.

  • To configure this destination using a template, select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

    Create Message

    Post a message to a text channel. Requires SEND_MESSAGES permission.

    • This endpoint automatically posts messages to a Discord text channel using data from your Nexset. No additional configuration is required beyond selecting this endpoint template.
    • The endpoint uses POST requests to https://discord.com/api/v10/channels/{channel_id}/messages where {channel_id} is the channel ID you configured in your credential. The endpoint URL is automatically constructed based on the Discord API base URL and the channel ID from your credential.
    • The endpoint sends data from your Nexset as the request body in JSON format. The request body is automatically formatted according to the schema fields and data mapping you configure. Each record in your Nexset will be sent as a JSON object containing the message data to post.
    • Batch mode is enabled by default for this endpoint (batch.mode: true), with a maximum of 1000 records per batch. When batch mode is enabled, multiple records from your Nexset can be combined into a single API request. The endpoint uses a body transformation function to combine multiple messages into a single message content.
    • This endpoint does not automatically create a data source to track the responses received from the Discord API after each call.

    The request body must be properly formatted JSON that matches the Discord API specification for creating messages. The endpoint requires OAuth2 authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. Discord API requests also require a User-Agent header in the format {bot_name} ({bot_url}, {bot_version}), which is automatically included based on your credential configuration. This endpoint requires the SEND_MESSAGES permission for the bot in the Discord server. Batch mode is enabled by default (batch.mode: true), which allows multiple messages to be combined efficiently. The channel ID is automatically retrieved from your credential configuration. For detailed information about creating messages, including required fields, field names, and request formats, see the Discord API documentation.

Configure Manually​

Discord destinations can be manually configured to send data to any valid Discord API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

With manual configuration, you can also create more complex Discord destinations, such as destinations that use custom request headers, different HTTP methods, or custom data formatting.

Content Format​

  1. Select the format in which the Nexset data will be sent to the Discord API from the Content Format pulldown menu. Nexla will automatically convert the data to the selected format for each API call. The Discord API typically uses JSON format for request bodies.

API Endpoint URL​

  1. Enter the URL of the Discord API endpoint to which you want to send the Nexset data in the URL field. This should be the complete URL including the protocol (https://) and any required path parameters. Discord API endpoints typically follow the pattern https://discord.com/api/v10/{endpoint_path}.

Ensure the API endpoint URL is correct and accessible with your current credentials. You can test the endpoint using the Test button after configuring the URL. The endpoint requires OAuth2 authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration. Discord API requests also require a User-Agent header in the format {bot_name} ({bot_url}, {bot_version}), which is automatically included based on your credential configuration. The bot must have the appropriate permissions in the Discord server to perform the actions you want to use. For detailed information about Discord API endpoints, authentication, and available APIs, see the Discord API documentation.