Integrations
Straight into Jira or ClickUp
Connect once over OAuth. On every confirmed draft, Prosody creates the issue in the right project, sprint and epic — asynchronously, with retries and a per-tenant circuit breaker so one integration outage never stalls another company's work.
Jira
Issues are created with your issue types and mapped to the active sprint under the correct epic, carrying the description, story points, due date and labels from the confirmed draft.
ClickUp
Tasks are created in the right list and sprint folder, carrying the same confirmed fields across from the draft.
Connect once over OAuth
An administrator authorises Prosody against your Jira or ClickUp workspace. The access and refresh tokens are encrypted at rest with Fernet and scoped to a single tenant — never stored in plaintext, never shared across companies. You can revoke access at any time, which disables ticket creation and nothing else.
Choose a default project or list
Point Prosody at the Jira project or ClickUp list where meeting follow-ups should land. That default is used unless a reviewer picks somewhere else while confirming a draft.
Sprint and epic placement
On confirm, Prosody resolves the active sprint and the right epic for the work and files the issue there, so items arrive where the team is already looking instead of in a backlog nobody triages.
Resilient, asynchronous creation
Creation happens in the background with retries and a per-tenant circuit breaker. If Jira or ClickUp has an outage, the work queues and retries; one company's integration problem never stalls another's. Every confirm, edit and reject is recorded and feeds prediction-accuracy analytics.
Jira and ClickUp are the only project tools Prosody writes to.