Which way the data moves
Before you connect a tool, it helps to know what it will change and where. Some integrations only read, one is a one-time move, and two work in both directions. This table sums up each one; its own page has the detail.
| Integration | Direction | What moves |
|---|
| Slack | Both ways | Ami answers in channels and direct messages, slash commands run attendance, task and timer actions as the linked member, and workflows post AmDital events to a connected channel. |
|---|
| Gmail | Into AmDital, read-only | Recent inbox and sent mail syncs every 15 minutes and attaches to the matching CRM contact. Nothing in your mailbox is sent, deleted or changed. |
|---|
| HubSpot | One-time import | Contacts, companies, deals and activities move into AmDital CRM, with deal stages mapped to your pipeline. Nothing is written back to HubSpot. |
|---|
| GreytHR | Both ways | AmDital check-ins go out as GreytHR swipes, and leave balances come back every four hours when leave sync is switched on. |
|---|
| GitHub | Links only | Repositories are linked to the projects they belong to. Pull requests, commits and branches are not synced. |
|---|
Who connects what
Some connections belong to the workspace and some belong to a person. GreytHR is set up once per workspace by an owner, admin or manager, and employees never connect their own GreytHR accounts. Gmail and GitHub are personal: each person connects their own account, so one person's mailbox or repositories are never shared with the team by default. Slack matches Slack users to AmDital members by email address, and anyone whose Slack account isn't linked yet is asked to connect before a command runs for them.
Before you switch one on
Check that people use the same email address in both tools. Slack, GreytHR and the Gmail contact matching all line records up by email, so a mismatch means a record that doesn't attach to the right person. If you are moving from HubSpot, set up your AmDital pipeline stages first, because the import asks you to map each HubSpot deal stage to one of them. And decide which tools you are keeping: CRM, HR, finance and projects are built-in modules on the same workspace record, so they need no integration at all.
When there is no native integration
The list above is short on purpose — a tool appears here only when its integration works today. For anything else, the REST API uses bearer-token auth with every request scoped to your workspace, and signed webhooks retry with backoff when your endpoint is down. AI clients such as Claude, ChatGPT and Cursor connect through the MCP server, each with its own scoped key that can expire and be revoked, and every call is recorded in the audit trail. The developer overview covers all three.
