# Build a Slack or Microsoft Teams Alert Payload

**Use case:** 

Convert one normalized signal into bounded UNSENT Slack, Microsoft Teams, or generic alert JSON without accepting secrets.

## Input

```json
{
  "schemaVersion": "1.0",
  "signal": {
    "signalId": "nike-recall-001",
    "signalType": "recall",
    "headline": "Nike issues a limited product recall",
    "summary": "The buyer supplied this normalized recall signal for review by a downstream operator.",
    "severity": "high",
    "occurredAt": "2026-08-05T12:00:00Z",
    "evidence": [
      {
        "url": "https://example.com/evidence/nike-recall-001",
        "title": "Buyer evidence record",
        "capturedAt": "2026-08-05T12:05:00Z"
      }
    ]
  },
  "target": "slack",
  "presentation": {
    "includeHeadline": true,
    "includeSummary": true,
    "includeSeverity": true,
    "includeSource": true,
    "includeOccurredAt": true,
    "maxContentChars": 600,
    "style": "standard"
  }
}
```

## Output

```json
{
  "schemaVersion": {
    "label": "Schema",
    "format": "text"
  },
  "reportType": {
    "label": "Report type",
    "format": "text"
  },
  "unsent": {
    "label": "Unsent",
    "format": "boolean"
  },
  "target": {
    "label": "Target shape",
    "format": "text"
  },
  "content": {
    "label": "Content",
    "format": "text"
  },
  "payload": {
    "label": "Target payload",
    "format": "json"
  },
  "sourceAttribution": {
    "label": "Evidence attribution",
    "format": "json"
  },
  "truncation": {
    "label": "Truncation",
    "format": "json"
  },
  "warnings": {
    "label": "Warnings",
    "format": "json"
  },
  "delivery": {
    "label": "No-send boundary",
    "format": "json"
  },
  "decision": {
    "label": "Review decision",
    "format": "json"
  },
  "inputDigest": {
    "label": "Input SHA-256",
    "format": "text"
  },
  "resultDigest": {
    "label": "Result SHA-256",
    "format": "text"
  }
}
```

## About this Actor

This example demonstrates how to use [Slack and Microsoft Teams Alert Payload Builder](https://apify.com/zinin/us-brand-signal-webhook-payload-builder) with a specific input configuration. Visit the [Actor detail page](https://apify.com/zinin/us-brand-signal-webhook-payload-builder) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
This Task's input is already configured above — use it as-is rather than inventing a new one.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/zinin/us-brand-signal-webhook-payload-builder.md

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).