When new message in SITE123, sync it to Shape.
When a new message is received in SITE123, push lead details into Shape CRM.
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.
SITE123 Explore SITE123 →
TriggersFires when a new page or post is published on SITE123.
Fires when a form on SITE123 is submitted.
Fires when a CMS item is updated on SITE123.
Publishes or updates a page on SITE123.
Creates a new CMS item on SITE123.
Updates existing content on SITE123.
Shape Explore Shape →
TriggersFires when a new contact or lead is added to Shape.
Fires when a field on a contact changes in Shape.
Fires when a deal, case or record moves to a new stage in Shape.
Fires when a deal is marked won in Shape.
Creates or updates a contact in Shape.
Creates a new deal in Shape.
Moves a deal or record to a new stage in Shape.
Logs a call, email, or note against a record in Shape.
More SITE123 + Shape workflows
See all SITE123 + Shape integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “When new message in SITE123, sync it to Shape.” between SITE123 and Shape?
Yes — describe it in the box above and Knit's Integrations Agent researches SITE123 and Shape'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 connecting Shape with SITE123 improve sales pipeline efficiency?
It eliminates manual data entry by converting web form submissions directly into qualified contacts and deals in your CRM.
Can updates in Shape change content published on SITE123?
Yes, updates to contacts or deals can automatically modify content items or publish new pages on your website.