Data sources
Connect the tools your team works in and keep memory in step with them.
A data source is a tool trellismem reads on your behalf. You choose what to include, and trellismem turns it into searchable memory and picks up changes on each sync.
Connect sources on the Integrations page.
What each source syncs
| Source | What becomes memory |
|---|---|
| Slack | Channels and threads |
| GitHub | Repository code and docs |
| Linear | Issues, comments and projects from the teams you select |
| Notion | The pages and databases you select |
| Google Drive | The folders and shared drives you select |
| Gmail | The labels you select |
| Google Calendar | Events in the calendars you select |
| Confluence | The spaces you select, their pages and comments |
| Jira | Issues and comments from the projects you select |
| HubSpot | Contacts, companies, deals and tickets |
| Salesforce | Accounts, contacts, opportunities and cases |
| Intercom | Conversations, contacts and help articles |
| Stripe | Customers, invoices and subscriptions |
Connecting a source
Each source card on the Integrations page lists the permissions it needs before you connect.
Most sources connect with an API token that you create in that tool and paste into the card. Use the narrowest token the tool offers. For Stripe, create a restricted, read-only key.
The Google sources (Drive, Gmail, Calendar) connect with Google sign-in instead.
After connecting, select what to include: channels, projects, spaces, folders or record types. Nothing is read until you select it.
Syncing
trellismem reads the selection and picks up changes on each sync. For Confluence and Salesforce, items deleted at the source are removed from memory too.
Credentials
Tokens are encrypted before they are stored. A connection belongs to the person who made it: you only ever see or disconnect your own.