Append campaign performance records into shared documents
When a contact enters a specific workflow or updates their preferences in Tars, append text details directly to the account overview page in Nexuss.
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.
Tars Explore Tars →
TriggersFires when a new lead or contact is captured in Tars.
Fires when a contact enters an automation in Tars.
Fires when a field on a contact changes in Tars.
Fires when a contact unsubscribes in Tars.
Creates or updates a contact in Tars.
Adds a contact to a workflow or campaign in Tars.
Sends an email or message to a contact via Tars.
Changes a contact's tags in Tars.
Nexuss Explore Nexuss →
TriggersFires when a new page or doc is created in Nexuss.
Fires when a new record is added to a database or table in Nexuss.
Fires when a doc in Nexuss is published or shared.
Fires when a status field changes on a record in Nexuss.
Starts a new page in Nexuss from a saved template.
Creates or updates a record in Nexuss.
Adds text to the end of an existing doc in Nexuss.
Moves a page in Nexuss into a different space.
More Tars + Nexuss workflows
Log newly captured leads into document tracking databases
When a new lead is captured in Tars, automatically add a record to your team's centralized lead tracker document in Nexuss.
See details
Launch campaign messages when documentation status changes
When a status changes to published on a document in Nexuss, automatically send an email or marketing campaign message via Tars.
See details
See all Tars + Nexuss integrations → · Browse the full workflow library →
Common questions
Can Knit build “Append campaign performance records into shared documents” between Tars and Nexuss?
Yes — describe it in the box above and Knit's Integrations Agent researches Tars and Nexuss'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 can new marketing leads automatically update doc databases?
Whenever a new lead is captured in Tars, a corresponding row or record is automatically created in your document database in Nexuss.
Can content updates in internal docs launch marketing messages?
Yes, when a document status changes or a new page is published in Nexuss, you can automatically update contact records or send messages in Tars.