Convert call follow-up items into support tickets
When a new item is captured during a call in Spiky.ai, automatically open a new ticket in Pylon for team resolution.
See all Spiky.ai + Pylon 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.
Spiky.ai Explore Spiky.ai →
TriggersFires when a new meeting is recorded in Spiky.ai.
Fires when an AI-generated summary is ready in Spiky.ai.
Fires when a meeting transcript is ready in Spiky.ai.
Fires when a new action item is captured from a meeting in Spiky.ai.
Uploads an audio or video file to Spiky.ai for transcription.
Pylon Explore Pylon →
TriggersFires when a new support ticket or chat conversation starts in Pylon.
Fires when a ticket's status changes in Pylon.
Fires when a ticket in Pylon is assigned to an agent.
Fires when a ticket in Pylon breaches its response SLA.
Creates a new ticket in Pylon.
Updates a ticket's status in Pylon.
Assigns a ticket in Pylon to an agent.
Posts a reply or internal note on a ticket or conversation in Pylon.
More Spiky.ai + Pylon workflows
See all Spiky.ai + Pylon integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Convert call follow-up items into support tickets” between Spiky.ai and Pylon?
Yes — describe it in the box above and Knit's Integrations Agent researches Spiky.ai and Pylon'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.
How does integrating Spiky.ai with Pylon help manage follow-ups after customer calls?
Key decision points and follow-ups captured by Spiky.ai during call recordings are converted automatically into support tickets within Pylon.
Can meeting notes from Spiky.ai be attached to existing support tickets in Pylon?
Yes, AI-generated summaries and transcripts from Spiky.ai can be posted automatically as detailed internal comments on related tickets in Pylon.