Connecting services
Slack, issue trackers and CRMs: how to connect them, and what they will and will not do.
Connections are made by an admin in Settings, Connections. Credentials are encrypted and shown once. Which services appear depends on what has been switched on for the service; see the integrations page for what is available now, coming soon and planned.
Slack
Add the app, choose one channel, and its messages become feedback in the review queue.
Issue trackers
GitHub is available; Linear, Jira Cloud, ClickUp, Asana and Azure DevOps follow the same pattern as each is switched on. Only one tracker can be connected at a time.
- Make a token or key in the tracker with permission to create issues in one repository, team or project.
- In Settings, enter the details. The connection is checked before it is stored.
- Some trackers need one more step on their side (for example adding a webhook); the screen shows the address and secret once.
- Choose which of your statuses a request moves to when the issue is done, and when it is reopened (or leave them alone).
- On a request page, choose Create an issue. The issue holds the title and counts and a link back, never quotes, names or emails.
If someone changes the request here after the link last agreed with the issue, a change from the tracker is held back and shown on the request for a person to settle; it is never overwritten. Moving into a shipped status prepares drafts for you to review; nothing is sent automatically.
CRMs (HubSpot, Salesforce)
Read-only account value; see People, accounts and value. The first sync starts within a minute of connecting and then runs daily; "Sync now" asks for another.
Sign-in
Email and password today. Company sign-in through your identity provider, and provider buttons, arrive when switched on.