Open onboarding support tickets for newly closed deals
When a deal is won in Google Contacts, automatically create a ticket in Alive5 so support engineers can initiate customer onboarding.
See all Alive5 + Google Contacts 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.
Alive5 Explore Alive5 →
TriggersFires when a new support ticket or chat conversation starts in Alive5.
Fires when a ticket's status changes in Alive5.
Fires when a ticket in Alive5 is assigned to an agent.
Fires when a ticket in Alive5 breaches its response SLA.
Creates a new ticket in Alive5.
Updates a ticket's status in Alive5.
Assigns a ticket in Alive5 to an agent.
Posts a reply or internal note on a ticket or conversation in Alive5.
Google Contacts Explore Google Contacts →
TriggersFires when a new contact or lead is added to Google Contacts.
Fires when a field on a contact changes in Google Contacts.
Fires when a deal, case or record moves to a new stage in Google Contacts.
Fires when a deal is marked won in Google Contacts.
Creates or updates a contact in Google Contacts.
Creates a new deal in Google Contacts.
Moves a deal or record to a new stage in Google Contacts.
Logs a call, email, or note against a record in Google Contacts.
More Alive5 + Google Contacts workflows
See all Alive5 + Google Contacts integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Open onboarding support tickets for newly closed deals” between Alive5 and Google Contacts?
Yes — describe it in the box above and Knit's Integrations Agent researches Alive5 and Google Contacts'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.
What business advantages come from linking Google Contacts and Alive5?
It breaks down silos between sales and support, giving account managers visibility into tickets and allowing closed sales to trigger onboarding workflows.
Can closing a deal automatically generate a ticket for customer success?
Yes, marking a deal as won in Google Contacts can automatically generate a ticket in Alive5 for implementation support.