# Microsoft Teams · Reply - Workflow node | Docs - nodulz

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

Language: en

Reply to the triggering conversation using the same bot.

## Usage and specifics

Use a Teams bot credential and activity or conversation parameters. The trigger receives Bot Framework activities at its published URL. Replies reuse the incoming activity context.

Technical type : `teams_response`. Runtime : `nodulz`.

## Credentials and prerequisites

- [Microsoft Teams bot](/docs/credentials) (`integration` / `teams_bot`). Single-tenant Azure Bot: encrypted tenant, client ID and secret

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` | - | - |
| `serviceUrl` | `string` | `""` | - |
| `conversationId` | `string` | `""` | - |
| `activityId` | `string` | `""` | - |
| `memberId` | `string` | `""` | - |
| `teamId` | `string` | `""` | - |
| `text` | `string` | `""` | - |
| `textFormat` | `enum` | `"markdown"` | `markdown`, `plain`, `xml` |
| `adaptiveCard` | `string` | `""` | - |
| `attachments` | `string` | `""` | - |
| `suggestedActions` | `string` | `""` | - |
| `method` | `enum` | `"GET"` | `GET`, `POST`, `PUT`, `PATCH`, `DELETE` |
| `path` | `string` | `""` | - |
| `body` | `string` | `""` | - |
| `replyToActivity` | `boolean` | `true` | - |

## Initial configuration

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

```json
{
  "credentialSource": "trigger",
  "serviceUrl": "",
  "conversationId": "",
  "activityId": "",
  "memberId": "",
  "teamId": "",
  "text": "",
  "textFormat": "markdown",
  "adaptiveCard": "",
  "attachments": "",
  "suggestedActions": "",
  "method": "GET",
  "path": "",
  "body": "",
  "replyToActivity": true
}
```

## 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)