When customer health metrics update in Vitally, update the account record in Pylon.
When customer health metrics update in Vitally, update the account record in Pylon.
4.9/5 on G2·
Google for Startups Accelerator
How 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.
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.
Vitally Explore Vitally →
TriggersFires when a new contact or lead is added to Vitally.
Fires when a field on a contact changes in Vitally.
Fires when a deal, case or record moves to a new stage in Vitally.
Fires when a deal is marked won in Vitally.
Creates or updates a contact in Vitally.
Creates a new deal in Vitally.
Moves a deal or record to a new stage in Vitally.
Logs a call, email, or note against a record in Vitally.
More Pylon + Vitally workflows
Open onboarding support tickets for newly closed deals
When a deal is won in Vitally, automatically create a ticket in Pylon so support engineers can initiate customer onboarding.
See details
Log activity in CRM when customer tickets are created
When a new ticket is created in Pylon, automatically log activity in Vitally so account managers stay informed of open customer issues.
See details
Update deal stages when critical support SLAs are breached
If an SLA is breached in Pylon, automatically update the deal stage in Vitally to alert sales leaders of potential account risks.
See details
See all Pylon + Vitally integrations → · Browse the full workflow library →
Common questions
Can Knit build “When customer health metrics update in Vitally, update the account record in Pylon.” between Pylon and Vitally?
Yes — describe it in the box above and Knit's Integrations Agent researches Pylon and Vitally'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 Vitally and Pylon?
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 Vitally can automatically generate a ticket in Pylon for implementation support.