# Discord response - Workflow node | Docs - nodulz

Source: https://nodulz.com/docs/nodes/discord_response

Language: en

Reply to the message or interaction that triggered the workflow.

## Usage and specifics

Use this node after a Discord trigger. Target the message or interaction that started the run. Keep the trigger context available to resolve the response.

Technical type : `discord_response`. Runtime : `nodulz`.

## Credentials and prerequisites

- [Create and configure the credential : discord-bot](/docs/credentials/discord-bot)

Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the [credentials guide](/docs/credentials) for access and rotation.

## Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

| Parameter | Type | Default | Values / limits |
| --- | --- | --- | --- |
| `credentialSource` | `enum` | `"trigger"` | `trigger`, `explicit` |
| `credentialId` | `string` | - | - |
| `target` | `enum` | `"auto"` | `auto`, `channel_message`, `interaction`, `interaction_followup`, `interaction_edit` |
| `content` | `string` | `""` | - |
| `embeds` | `array` | `[]` | - |
| `embeds[].title` | `string` | `""` | - |
| `embeds[].description` | `string` | `""` | - |
| `embeds[].url` | `string` | `""` | - |
| `embeds[].color` | `string` | `""` | - |
| `embeds[].timestamp` | `boolean` | `false` | - |
| `embeds[].footer` | `string` | `""` | - |
| `embeds[].footerIconUrl` | `string` | `""` | - |
| `embeds[].imageUrl` | `string` | `""` | - |
| `embeds[].thumbnailUrl` | `string` | `""` | - |
| `embeds[].authorName` | `string` | `""` | - |
| `embeds[].authorUrl` | `string` | `""` | - |
| `embeds[].authorIconUrl` | `string` | `""` | - |
| `embeds[].fields` | `array` | `[]` | - |
| `embeds[].fields[].name` | `string` | `""` | - |
| `embeds[].fields[].value` | `string` | `""` | - |
| `embeds[].fields[].inline` | `boolean` | `false` | - |
| `ephemeral` | `boolean` | `false` | - |
| `responseTemplate` | `string` | `""` | - |

## Examples

- Example: {{ input.message.content }} or {{ input.member.username }}

## Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

```json
{
  "credentialSource": "trigger",
  "target": "auto",
  "content": "",
  "embeds": [],
  "responseTemplate": ""
}
```

## Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.

See also : [Expressions and data](/docs/expressions), [Executions](/docs/executions), [Node catalog](/docs/nodes).

## Explore further

- [Features - nodulz](https://nodulz.com/product/overview)
- [Node catalog - nodulz](https://nodulz.com/product/catalog)
- [MCP server - nodulz](https://nodulz.com/product/mcp)
- [Pricing - nodulz](https://nodulz.com/pricing)
- [Use cases and workflow automation - nodulz](https://nodulz.com/use-cases)
- [Choose what your workflows can do. - nodulz](https://nodulz.com/compare)
- [Documentation - nodulz](https://nodulz.com/docs)