Integrations
Integrations
Connections are how Sands does work in your tools. Each one uses the tool's own sign-in, works with the access you grant, and follows the same rules.
Available today
Jira
Projects, issues, worklogs and hours reports. Plans become epics and stories.
Linear
Teams, projects and issues. Plans become a project with milestones and issues.
Asana
Projects, sections and tasks. Plans become a project with sections and tasks.
Slack
Read channels and threads, send messages and reactions, and use Sands in Slack.
What each connection can do
| Jira | Linear | Asana | Slack | |
|---|---|---|---|---|
| Read and search | Yes | Yes | Yes, search on paid Asana plans | Channels and threads |
| Create items | Yes | Yes | Yes | Messages |
| Assign, move, edit, comment | Yes | Yes | Yes | Reactions |
| Create a project | Yes | When sending a plan | Yes | |
| Receive a plan | Yes | Yes | Yes | |
| Hours reports | Yes |
Connecting
Connect from any of these places. They all open the same short connect step:
- + in the composer, then the tool.
- Settings → Connectors.
- The card Sands shows when a request needs a tool you have not connected. After you connect, Sands carries on with the request.
- Send to in a plan, for project tools.
The connect step names what Sands will be able to do, then opens the tool's sign-in in a pop-up. Approve it and you are back in Sands. If the pop-up is blocked, Sands tells you and offers to try again.
Rules every connection follows
- Read first: answers and plans are grounded in what Sands reads from your tool.
- Your approval mode decides whether a change runs right away or waits for your OK.
- Changes are read back after they run and reported as they landed, with a link.
- Each change runs once, even when a request is retried.
- Sands never acts on a project, ticket or channel it guessed at. If a name is unclear, it asks.
- Tokens are stored encrypted and scoped to your account.
Expired connections
Tools sometimes expire access. When that happens mid-request, Sands shows one card asking you to reconnect, and the request picks up where it stopped without doing anything twice. In the + menu and in Settings, the tool shows Reconnect.
Disconnecting
Disconnect any tool from Settings → Connectors. Sands stops using it straight away. You can also revoke access from the tool's own settings.
Need another tool?
monday.com, GitHub, Confluence and others are on the roadmap. Tell us which one you need and for what at hello@sandsai.co or with the feedback button.