What happens if Slack changes their API after we go live?
Our SRE team monitors Slack change announcements and rolls compatibility updates inside our maintenance retainer. If a breaking change ships, we own the migration; you don't pay extra to stay current and you don't field calls from the vendor.
What does pricing look like?
Implementation is fixed-fee with a $0-until-live guarantee for Phoenix, 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.
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.
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.
Is this a packaged Slack connector or a custom build?
It is a Connectify-owned adapter, not a third-party packaged connector. We maintain the code, we monitor the runtime, and the fields, hooks, and reconciliation rules are shaped to your exact data model — not a generic schema we hope matches.
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.