Integrations
Integrations let Pulse work with the tools your team already uses. Connect providers at the workspace level so the assistant can read relevant information, prepare updates, and take approved actions from the same timeline.
What this is
An integration is a managed connection between Pulse and an external tool such as Slack, GitHub, Notion, Jira, Google Drive, or a CRM. Once connected, Pulse can use that provider during conversations, tasks, and approval-driven workflows.
When to use it
Connect an integration when you want Pulse to:
- Summarize activity from an external system.
- Draft or post updates in a communication tool.
- Create, update, or review records after approval.
- Pull context from project, CRM, storage, or knowledge tools.
- Run scheduled work that depends on another product.
Before you start
Make sure:
- You have permission to connect the provider.
- You know which workspace or account should be connected.
- You understand what Pulse should be allowed to read or change.
- Sensitive write actions are protected by approval policies.
Connect an integration
- Open Settings.
- Select Integrations.
- Choose the provider you want to connect.
- Authorize the provider with OAuth or the credential method shown in the product.
- Review the requested access.
- Save the connection.
- Run a small test task from the timeline.
TIP
Connect only the providers a workspace actually needs. For tools that can change customer records, send messages, or spend money, pair the integration with approval policies before rollout.
Provider categories
| Category | Examples |
|---|---|
| Communication | Slack |
| CRM | Salesforce, HubSpot, Pipedrive |
| Project management | Jira, Trello, Notion |
| Developer collaboration | GitHub |
| Storage | Google Drive |
| Knowledge | Knowledge bases and wikis |
| Operations | Monitoring and observability platforms |
Review or test the result
After connecting a provider, ask Pulse for a low-risk task:
Summarize the open issues assigned to me and show the draft here.Review whether Pulse found the right source, used the right workspace, and returned the result in the timeline. If the task would write to another tool, verify that an approval appears before the action runs.
Troubleshooting
The provider is not available
Check whether the integration is enabled for your workspace and whether your role allows you to manage integrations.
Authorization fails
Confirm that you are signed into the correct provider account and that your provider admin allows third-party connections.
Pulse cannot find the expected data
Review the connected workspace, project, repository, folder, or account. Many providers scope access to a specific workspace or resource during authorization.
A write action runs without the expected approval
Pause rollout and review approval policies. Sensitive actions should require a human decision before Pulse writes to an external system.
Related
- Skills
- Approvals
- Settings & administration
- Developer Hub for custom integration implementation