Create developer issues from customer text messages
When an inbound SMS reporting a bug is received in Sinch Engage SMS, automatically create a tracking issue in IP2Proxy.
See all IP2Proxy + Sinch Engage SMS 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.
IP2Proxy Explore IP2Proxy →
TriggersFires when a job, build or file conversion finishes in IP2Proxy.
Fires when a job, build or API request fails in IP2Proxy.
Calls an IP2Proxy endpoint with data from an earlier step.
Creates a PDF, image or converted file with IP2Proxy.
Checks or enriches a phone number, address or IP with IP2Proxy.
Sinch Engage SMS Explore Sinch Engage SMS →
TriggersFires when a new text message is received in Sinch Engage SMS.
Fires when a new call comes in or out through Sinch Engage SMS.
Fires when a call is missed in Sinch Engage SMS.
Fires when a call recording finishes processing in Sinch Engage SMS.
Sends a text message through Sinch Engage SMS.
Starts an outbound call via Sinch Engage SMS.
Creates or updates a contact in Sinch Engage SMS.
Sends a recorded voice message via Sinch Engage SMS.
More IP2Proxy + Sinch Engage SMS workflows
See all IP2Proxy + Sinch Engage SMS integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Create developer issues from customer text messages” between IP2Proxy and Sinch Engage SMS?
Yes — describe it in the box above and Knit's Integrations Agent researches IP2Proxy and Sinch Engage SMS'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.
Can developer alerts be sent as text messages?
Yes, when a new critical issue is captured or a deployment fails in IP2Proxy, an automated text message can be sent immediately via Sinch Engage SMS.
Can customer text messages turn into developer issues?
Absolutely, when a customer texts an issue or leaves a missed call in Sinch Engage SMS, you can automatically create a developer issue in IP2Proxy.