Send signals from Slack & Teams

​

Prerequisites

• A Clarifeye knowledge store, and its project ID (the store’s UUID).
• An API token with access to that store. See MCP authentication for how to issue one — the same Authorization: Bearer <token> credential works for the REST API.
• The ability to build and install an app in your Slack workspace or Microsoft Teams tenant.

​

The API call

POST https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/signals/

curl -X POST \
  "https://eu.app.clarifeye.ai/api/v1/projects/$PROJECT_ID/signals/" \
  -H "Authorization: Bearer $CLARIFEYE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "feedback": "The refund policy in the store is out of date — EU orders are now 30 days, not 14.",
    "context": { "source": "Slack" }
  }'

const res = await fetch(
  `https://eu.app.clarifeye.ai/api/v1/projects/${projectId}/signals/`,
  {
    method: "POST",
    headers: {
      Authorization: `Bearer ${process.env.CLARIFEYE_TOKEN}`,
      "Content-Type": "application/json",
    },
    body: JSON.stringify({
      feedback:
        "The refund policy in the store is out of date — EU orders are now 30 days, not 14.",
      context: { source: "Slack" },
    }),
  }
);

​

Send it from Slack or Teams

• Slack — build a Slack app (for example a slash command or a message shortcut) that POSTs to the endpoint. See Slack’s Create an app guide to build and install it.
• Microsoft Teams — build a Teams app (a bot, message action, or message extension) that POSTs to the endpoint. See Microsoft’s Build apps for Microsoft Teams guide.

​

Where to find your project ID and token

• Project ID — the UUID of the knowledge store you want signals to land in. You can find it in the store’s URL in the Clarifeye app.
• API token — issue one from your account settings and send it as Authorization: Bearer <token>. See MCP authentication for the full walkthrough; the same token authenticates the REST API.