Docs / Configure

Integrations

Connections to external tools: Slack, Jira, GitHub, Microsoft Teams, Telegram and Discord. For Slack, Teams, Telegram and Discord you choose which events are sent. Jira and GitHub can open an issue for each new story and keep its status in step.

When to use it

When you want project events to appear where the team already works, or stories mirrored as Jira or GitHub issues.

Start here

Pick a tool and connect it. Slack, Jira and GitHub connect through a sign-in popup; Teams and Discord need a webhook URL; Telegram needs a bot token and chat ID. For Jira and GitHub, click Configure to turn on auto-create.

How to use it

  1. Find the provider card you want. The page lists Slack, Jira, GitHub, Microsoft Teams, Telegram and Discord, each with a status badge such as "Not connected" or "Active".
  2. For Slack, Jira and GitHub, click "Connect via OAuth" and complete the sign-in in the popup window. The popup then returns to Wevit to confirm the connection; it only completes for the same Wevit user who started it. If a Jira or GitHub card shows an error, click "Reconnect" and sign in again.
  3. For Microsoft Teams and Discord, click "Configure Webhook" and paste the provider's own webhook URL (other addresses are refused). For Telegram, click "Configure Bot" and enter the "Bot Token" and "Chat ID". Then click "Save & Test".
  4. Once a connection is Active, click "Configure" on its card to open the settings panel.
  5. For Slack, Teams, Telegram and Discord, tick the "Notification Events" you want sent, then click "Save Configuration". If no events are ticked, all events are sent.
  6. For Jira, enter the "Jira Project Key" and pick a "Default Issue Type". For GitHub, enter the "Repository" as owner/repository. Tick "Auto-create Jira issues when stories are created" or "Auto-create GitHub issues when stories are created", then click "Save Configuration".
  7. To keep status in step both ways, tick "Bidirectional sync". Then, in the panel's inbound webhook section, click "Generate webhook secret" and register the URL it shows in Jira (WebHooks) or GitHub (repository Webhooks).
  8. Use "Test" on an active card to run a connection test, "Logs" to load its entries into the "Sync Logs" table, and "Disconnect" (then confirm) to remove a connection.

Good to know

  • Notification events you can choose: Story completed, Story in review, PRD approved, Sprint plan published, Story review approved, Changes requested on story, and Approval decided.
  • With auto-create on, a story created in Wevit opens a Jira or GitHub issue within about 15 seconds, and its key shows as a link on the story's row in the backlog. Excel import, bulk import, AI generation and the RFP converter do not send stories.
  • Wevit stays the source of truth for a story's title and description: edits made in Wevit are pushed, edits made in Jira or GitHub are not applied back. Only status goes both ways, and Jira or GitHub never move a story that is in review or in QA backwards.
  • You register the webhook yourself. The URL and secret are shown once and generating a new secret stops the old webhook working. "Last delivery received" shows when Jira or GitHub last reached Wevit.
  • The "Sync Logs" table shows direction, event type, status, duration, time and any error. A failed send is retried with growing delays, gives up after five attempts, and the card then shows the error.

Related

Last updated 6 October 2026