Esc

↑↓ move↵ openIndex · Pagefind
← All integrations

Productivity

Slack

Planned

Conversation references under evaluation.

Planned. This connection is not available in os.construction yet. This page describes the intended scope; it is not a release date.

Coverage by service or edition

Scope under evaluation. Each service needs its own permissions and acceptance checks.

  • Slack

    Planned

    Conversation references under evaluation.

Prepare for a scoped walkthrough

Use this checklist to agree the scope. These are preparation steps, not instructions for an available authorization or sync screen.

  • Token scopes, conversation membership and retention expectations.
  • Confirm the destination company/project and the reviewer responsible for approving imported records.
  1. Confirm the scope

    Token scopes, conversation membership and retention expectations.

  2. Agree the mapping

    Team/channel/ts → message key; thread_ts → parent; timestamps remain strings.

  3. Preview and reconcile

    Keep source identity/revisions separate from locally owned permissions, project placement and workflow decisions. Unresolved associations or conflicting local edits require review.

  4. Review before applying

    An authorized reviewer must confirm destination scope, unresolved records and control totals. A successful extraction is not proof that data has been applied.

  5. Check recovery and access

    Pause on expired or revoked access. Restore authorization before resuming from the last complete checkpoint. An incomplete list or permission error is not proof of deletion; inspect uncertain outcomes before retrying.

Mapping and synchronization

Record mapping

Team/channel/ts → message key; thread_ts → parent; timestamps remain strings.

Sync boundary
Follow next_cursor after short/empty pages; history/replies and rate limits differ.
Source ownership
The provider remains authoritative for its source records. Local project placement, access and workflow decisions need explicit destination ownership. Match by scoped IDs, not names alone.
Outbound policy
No provider business writes are offered here. Sending, posting, inviting, deleting and permission changes require separately approved capabilities.

Conflicts and recovery

When records disagree

Keep source identity/revisions separate from locally owned permissions, project placement and workflow decisions. Unresolved associations or conflicting local edits require review.

When a run stops

Pause on expired or revoked access. Restore authorization before resuming from the last complete checkpoint. An incomplete list or permission error is not proof of deletion; inspect uncertain outcomes before retrying.

Limits to plan around

  • No sending, invitations or channel changes. Complete history may be unavailable.
  • Not available in os.construction yet. Provider documentation describes the upstream API, not an os.construction connection.

No provider connection is initiated from this page. For the reviewed accounting import workflow available today, see the accounting import guide.

Documentation and source dates

Provider documentation establishes upstream capabilities, not os.construction availability. Confirm the current edition and API contract before planning setup.

Back to integration directory
Open file