Integrations
The seven integration cards, what each one really does, and how configuration persists.
Integrations
Where
/dashboard/integrations. Each card has its own configuration schema, a test action and a draft state you can publish later. Configuration persists to your account preferences, so it survives reloads and is scoped to you rather than to the browser.
The cards
- Slack — incoming webhook URL, channel name and subscribed events.
- GitHub — repository URL, default branch, and auto-linking of PRs that mention task ids.
- Jira import — site URL and project key. Configuration-only in this build: no call is made to Atlassian APIs. Use the CSV importer for real data movement.
- Google Calendar — include task due dates and sprint boundaries. Produces an internal feed URL; no Google sync happens in this build.
- Webhooks — endpoint URL, optional signing secret and subscribed events.
- CSV bulk tasks — delimiter and whether to skip invalid rows. This is the real importer.
- Zapier — catch-hook URL and trigger event.
Lifecycle of a configuration
- Open the card and fill in the fields. Required fields are marked.
- Save. The live configuration is updated and a toast confirms it.
- Or save as draft — the page then shows a drafts banner and nothing changes until you publish.
- Test the connection from the same dialog to see whether the endpoint answers.
Events
The subscribed-event list is shared across the Slack, Webhooks and Zapier cards, so an event name means the same thing everywhere. Notifications are the source of most of them: a task created, a sprint started, a role changed.
Reading it programmatically
- GET /api/integrations returns the saved configurations.
- PUT /api/integrations/<key> saves one.
- POST /api/integrations/test runs the test action.
- POST /api/integrations/import runs the CSV import.
Honest limits
- No OAuth flows. Credentials you enter are stored as configuration for that card.
- No two-way sync. Jira and Google Calendar are configuration surfaces in this build.
- Webhook delivery is outbound to the URL you supply; there is no inbound webhook receiver other than the routes listed in the endpoint reference.