Send secondary voice messages after completed recordings
When a call recording is ready in Connectix, automatically send a voice message in respond.io to follow up on secondary service lines.
See all Connectix + respond.io integrations or talk to a human
Opens Claude with Knit filled in: click Continue. Claude web and desktop share one connector list. Or paste this link in Settings > Connectors > Add custom connector.
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents claude
Run in your own terminal, then restart Claude Code. Adds the server, the Knit skill and a CLAUDE.md note.
Turn on developer mode, then create a connector named Knit with this link and No Auth.
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents codex
Run in your own terminal (not through Codex), then start a new Codex session.
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents antigravity
Run in your own terminal, then reload MCP servers (/mcp in the CLI, refresh in the IDE).
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents cursor
Run in your own terminal, restart Cursor, then paste the note it prints into User Rules.
Google for Startups AcceleratorHow Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Connectix Explore Connectix →
TriggersFires when a new text message is received in Connectix.
Fires when a new call comes in or out through Connectix.
Fires when a call is missed in Connectix.
Fires when a call recording finishes processing in Connectix.
Sends a text message through Connectix.
Starts an outbound call via Connectix.
Creates or updates a contact in Connectix.
Sends a recorded voice message via Connectix.
respond.io Explore respond.io →
TriggersFires when a new text message is received in respond.io.
Fires when a new call comes in or out through respond.io.
Fires when a call is missed in respond.io.
Fires when a call recording finishes processing in respond.io.
Sends a text message through respond.io.
Starts an outbound call via respond.io.
Creates or updates a contact in respond.io.
Sends a recorded voice message via respond.io.
More Connectix + respond.io workflows
See all Connectix + respond.io integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Send secondary voice messages after completed recordings” between Connectix and respond.io?
Yes — describe it in the box above and Knit's Integrations Agent researches Connectix and respond.io's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
Why connect two different phone and SMS platforms?
Linking Connectix with respond.io lets teams bridge separate communication systems, cross-notify staff about missed calls, and keep contact records consistent across carriers.
Can I automatically send texts from one platform when calls are missed on another?
Yes, a missed call detected in Connectix can immediately instruct respond.io to dispatch an automated text reply.