Can the Slack adapter handle our custom fields?
On first connection the adapter discovers every custom field, custom object and custom workflow inside your Slack tenant and presents them as first-class mappings — you decide which to mirror, which to ignore, and which to enrich.
How long does the Slack integration take to ship?
Our standard window is thirty days from signed scope to live Slack adapter in production, plus a one-week monitored stabilization phase. For Peoria, Arizona, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.
How is data security handled?
Tokens and credentials live inside a hardware-backed secret store with audit logging on every read. The Slack adapter runs on isolated workers with deny-by-default egress, and every message is replayable from a tamper-evident journal for downstream forensics.
What does pricing look like?
Implementation is fixed-fee with a $0-until-live guarantee for Peoria, Arizona. After go-live, the Slack adapter runs on a flat monthly run-rate sized to message volume — no per-API-call gotchas, no per-seat surcharges, and a one-page exit clause.
Do we own the integration code at the end?
Yes. The Connectify Slack adapter ships with full source escrow rights — at any point you can request a snapshot of the code, configuration, and runbooks. We prefer you stay on our managed runtime, but you are never locked in.
Does it work with our existing Slack licenses?
Yes — the adapter rides on top of your existing Slack subscription. We use service-principal or OAuth M2M credentials so the integration never burns a named-user seat and never pushes you into a higher tier.