Does X Integrate With Y?

Slack supports Google Drive sharing and previews so files can be posted and discovered inside channels. Permission behavior depends on your Google Workspace settings.

Dropbox file links can be shared with previews and quick actions in Slack. Teams often standardize on one storage provider to keep permissions predictable.

Slack can receive GitHub notifications (PRs, issues, deployments) and supports interactive workflows in channels. The exact capabilities depend on which app/config you install.

Jira issues can be created and updated from Slack with notifications and link previews. For teams choosing a tracker, see: Jira vs Linear.

Linear can post issue updates and automate notifications into Slack channels. This is commonly used for engineering triage workflows.

Asana tasks can be pushed into Slack with updates and reminders. If you’re comparing project tools, see: Trello vs Asana.

Trello card updates can be posted to Slack and you can take basic actions from messages. Power‑ups and app permissions may affect what’s available.

Slack supports Zoom meeting notifications and quick actions (start/join) in channels. Admin settings can restrict what users can connect.

Calendly can send booking notifications into Slack channels or DMs. Useful for sales/support scheduling updates.

Stripe events (payments, disputes, subscriptions) can be pushed to Slack for revenue ops alerts. For enterprise messaging comparisons, see: Slack vs Microsoft Teams.

Teams is optimized for Microsoft 365 storage (OneDrive/SharePoint). Google Drive workflows usually rely on third‑party connectors rather than first‑party integration.

Teams can receive GitHub notifications and enable basic collaboration around PRs/commits using apps and connectors.

Jira notifications can be delivered into Teams channels using apps/connectors. If you’re comparing messaging platforms, see: Slack vs Microsoft Teams.

Teams can integrate with Zoom for meeting scheduling and notifications, but many orgs standardize on Teams meetings for simplicity.

Asana task updates can be surfaced in Teams channels through apps and connectors. Some actions may require leaving Teams to complete.

Trello boards can be connected to Teams channels to display cards and updates. Experience varies depending on the Trello app setup.

Notion supports embedding and linking Google Drive files. Permission access is controlled by Google Workspace.

Notion can connect to GitHub via automations and embeds to track PRs/issues in docs. Depth depends on the workflow tool you use.

Notion can reference Jira issues and sync status fields using integrations and automations. Teams choosing trackers often compare: Jira vs Linear.

Linear issues can be linked/embedded in Notion to connect planning docs and execution. This is common for product requirements.

Asana tasks can be connected to Notion for reporting dashboards and documentation. Some syncs require third‑party automation.

Trello boards/cards can be embedded or synced into Notion via connectors. This is often used for lightweight reporting.

Dropbox files can be linked or embedded inside Notion pages. For rich permission management, confirm sharing rules in Dropbox.

Notion pages can include Zoom meeting links and notes; meeting automation typically uses calendar tooling and webhooks.

Notion does not provide a native Shopify integration. Teams usually rely on exports or automation tools to sync store metrics into docs.

Jira can connect to GitHub to link PRs/commits to issues and improve traceability. The setup may vary by plan and configuration.

Jira can integrate with GitLab for linking merge requests and deployment events. Some teams prefer simpler workflows with Linear.

Jira issues can be surfaced in Notion docs via connectors and automation. Useful for product documentation and weekly reporting.

There is no universal, first‑party Jira↔Linear integration. Teams usually migrate rather than run both. See: Jira vs Linear.

Jira can connect to Google Drive via attachments and marketplace apps. For strict permission control, validate your workspace sharing settings.

Zapier can automate Jira workflows (create issues, update fields, notify other tools) with common triggers. Good for lightweight integrations.

Make can orchestrate Jira automations across multiple systems (forms, CRMs, chat). Useful when you need custom mapping.

Linear provides deep GitHub integration to link PRs/commits to issues. This is often compared against Jira’s ecosystem: Jira vs Linear.

Linear can connect to GitLab for linking merge requests and issue references. Depth varies by workflow and permissions.

Linear issues can be embedded and tracked inside Notion docs for planning and specs. Common for product teams.

Linear can link to Drive docs in issues and descriptions. For bi‑directional sync, automation tools may be required.

Linear does not typically offer a first‑party Jira integration. Most teams choose one tracker and migrate. See: Jira vs Linear.

Zapier can automate Linear workflows (create issues from forms, sync status to other tools). Useful for low-code integrations.

Make can automate Linear across chat, docs, and CRM tools. Useful for custom multi-step workflows.

Asana supports attaching Google Drive files to tasks and projects. Permissions follow Google Workspace settings.

Dropbox files can be attached to Asana tasks for design assets or docs. This helps centralize context per task.

Notion can mirror Asana tasks into docs via connectors. Useful for status dashboards and meeting notes.

Asana and Trello generally do not have a simple first‑party sync. Teams typically pick one tool. See: Trello vs Asana.

Asana can connect to GitHub for linking work items to pull requests. Depth depends on your setup and plan.

Zapier can automate Asana task creation and status syncing across forms, email, and chat. Good for lightweight operations workflows.

Calendly events can create tasks or notifications in Asana through automation tools. Useful for intake workflows.

Trello cards can attach Google Drive files for specs and assets. Permissions follow Google Workspace.

Dropbox files can be attached to Trello cards. This is useful when teams store creative assets in Dropbox.

Notion can embed Trello boards/cards and automate updates. Helpful for combining docs and kanban.

Trello and Asana typically require third‑party automation for any sync. Many teams choose one. See: Trello vs Asana.

GitHub activity can be connected to Trello via Power‑Ups and automation tools to keep development and planning aligned.

Zapier can automate Trello card creation and movement based on triggers from other apps.

Make can automate Trello workflows with custom mapping across many apps. Useful for complex boards and multiple lists.

GitHub can link commits and pull requests to Jira issues to improve traceability. Some capabilities depend on admin settings.

GitHub integrates with Linear to automatically update issues based on PRs and commits. This is a major selling point for Linear.

GitHub issues/PRs can be embedded or synced into Notion docs via automation tools for reporting.

GitHub and GitLab are competing platforms; there’s no typical first‑party integration. Teams often migrate rather than sync.

Zapier can automate GitHub workflows (create issues from forms, notify CRM, post to chat). Helpful for ops.

GitHub does not provide a native Stripe integration; payment/event workflows typically rely on webhooks and automation tools.

GitLab can link Jira issues to merge requests and deployments. Useful for traceability across planning and delivery.

Notion can surface GitLab activity via embeds and automation (issues, MRs, deployments).

GitLab can connect to Linear for linking merge requests to issues. Helpful for engineering planning.

Zapier can automate GitLab updates into chat and docs. Useful for lightweight ops workflows.

GitLab does not natively integrate with Google Drive; teams usually connect via links or automations.

Drive files can be embedded/linked in Notion, and automations can sync updates into docs.

Asana supports attaching Drive files to tasks so teams can find specs and assets without hunting through folders.

Trello supports attaching Drive files to cards. This is commonly used for collaborative docs.

Zapier can automate Drive workflows (new file triggers, folder monitoring) to send updates to other tools.

Google Drive and Dropbox are competing storage tools; direct sync typically requires third‑party migration/automation rather than a first‑party integration.

Dropbox files can be linked or embedded in Notion pages. Automations can help keep links organized.

Dropbox files can be attached to Asana tasks for shared assets and documentation. Permissions follow Dropbox sharing.

Dropbox attachments in Trello cards help keep assets close to work items. Useful for creative workflows.

Dropbox and Google Drive generally do not have a simple first‑party sync. Teams usually pick one, or use migration tools.

Zapier can automate Dropbox file events (new file, folder change) to trigger actions in other tools.

Zapier can sync Notion database updates into other tools and vice versa. Useful for lightweight CRM and tracking.

Zapier supports Drive triggers/actions (new file, new folder, upload) for connecting storage to workflows.

Zapier can create and update Jira issues from external triggers. Good for intake forms and notifications.

Zapier can automate Linear tasks from forms, emails, and internal tools. Useful for connecting ops to engineering.

Zapier can connect Shopify order events to Slack, spreadsheets, and CRMs. Useful for ecommerce ops.

Zapier can connect Stripe events to other tools without custom code. Great for notifications and simple automations.

Make can sync Notion databases and automate workflows across multiple tools with custom mapping.

Make supports Drive triggers/actions and can orchestrate file pipelines into other tools.

Make can automate Jira issue creation and updates with complex rules and data mapping.

Make can automate Linear workflows across chat, docs, and forms. Good for cross‑team processes.

Make can sync Shopify orders/customers into other systems and trigger operational workflows.

Make can consume Stripe webhooks and route events to multiple destinations. Useful for multi-step revenue ops.

Zoom cloud recordings can be connected to Drive workflows via automations. Exact storage routing depends on your setup.

Zoom can integrate with Teams for scheduling and notifications, though many orgs choose one meeting platform.

Calendly can automatically create Zoom meeting links for bookings and notify participants.

Zoom meeting links and notes can live in Notion pages; automation typically uses calendar/webhook tools.

Calendly doesn’t directly integrate with Google Drive as a storage system; file workflows usually go through calendar + automation tools.

Calendly can send booking alerts to Slack channels and DMs. Helpful for sales/support teams.

Calendly events can be logged into Notion databases via automations for reporting and follow‑ups.

Calendly can use Stripe to collect payments for paid bookings depending on your plan and configuration.

Shopify events can be pushed into Slack for order alerts, refunds, and operational notifications.

Shopify does not have a native Google Drive integration. Teams usually export data or use automation tools for syncing reports.

Zapier can connect Shopify order events to CRMs, spreadsheets, and chat channels without custom code.

Make can orchestrate Shopify workflows across fulfillment, marketing, and analytics tools.

Stripe integrates well with automation platforms for routing payment events to tools like Slack, Notion, and CRMs.

Stripe data can be synced into Notion databases via automation tools for lightweight reporting. Avoid storing sensitive payment data in docs.

Shopify and Stripe can be connected in some setups, but it’s not a universal first‑party integration. Many workflows use middleware.

Airtable and Notion can sync data through automation tools. Useful for reporting dashboards and lightweight CRMs.

Drive attachments can be linked in Airtable records, and automations can connect file events to database updates.

Zapier can create Airtable records from forms and sync updates to other tools. Popular for operations workflows.

Make can orchestrate multi-step Airtable automations with custom mapping, useful for complex pipelines.

Obsidian vaults can be stored/synced via file storage workflows, but reliability depends on how sync is configured.

Obsidian files can be stored in Dropbox, but real-time collaboration and conflict handling depend on your sync approach.

Obsidian vaults can be versioned with GitHub using git-based workflows. This is common for technical teams.

Obsidian does not have a first‑party Slack integration. Teams usually connect via automation tools or shared links.

ClickUp can attach Google Drive files to tasks and docs. Permission behavior depends on your Drive settings.

ClickUp can link tasks with GitHub PRs and commits for traceability, depending on your integration setup.

Zapier can automate ClickUp tasks from forms and other tools. Useful for cross-team intake and operations.

Figma designs can be linked into Jira issues, and some setups enable richer previews in tickets. Useful for product delivery.

Figma files can be embedded in Notion pages to keep specs and designs in one place.

Figma files can be linked in Asana tasks for design handoff. Automations can notify teams when designs change.

Miro integrates with Jira to convert sticky notes into issues and sync status back to boards.

Miro boards can be embedded in Notion, and automation tools can connect board updates to docs.

Miro can connect to Asana to turn workshop outcomes into tasks. Useful for planning sessions.