Create tickets from rows
When a new row is added in RowShare, create a ticket in Intercom.
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.
RowShare Explore RowShare →
TriggersFires when a row is added to a sheet in RowShare.
Fires when a row or column changes in RowShare.
Fires when a new spreadsheet or worksheet is created in RowShare.
Adds a new row to a sheet in RowShare.
Updates the values in an existing row in RowShare.
Finds a row by a column value in RowShare.
Intercom Explore Intercom →
TriggersFires when a new support ticket or chat conversation starts in Intercom.
Fires when a ticket's status changes in Intercom.
Fires when a ticket in Intercom is assigned to an agent.
Fires when a ticket in Intercom breaches its response SLA.
Creates a new ticket in Intercom.
Updates a ticket's status in Intercom.
Assigns a ticket in Intercom to an agent.
Posts a reply or internal note on a ticket or conversation in Intercom.
More RowShare + Intercom workflows
See all RowShare + Intercom integrations → · Browse the full workflow library →
Common questions
Can Knit build “Create tickets from rows” between RowShare and Intercom?
Yes — describe it in the box above and Knit's Integrations Agent researches RowShare and Intercom'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 tickets be logged?
Yes. New or updated tickets in Intercom can be added as rows in RowShare.
Can a row open a ticket?
When a row is added in RowShare, Intercom can create a ticket.