Vitally

Vitally + Konnectify

Vitally Integration with Konnectify

Connect Vitally’s B2B Customer Success workspace to Konnectify to keep Organizations, Accounts, Users, tasks, notes, NPS responses, and conversations automatically in sync across your SaaS stack.

Organizations Accounts Users Notes Projects NPS Responses Tasks Messages Conversations Custom Objects 19 Triggers 36 Actions

ON THIS PAGE

→ What is Vitally? → API & Authentication → How to connect → Triggers (19) → Actions (36) → Popular automations → FAQ

What is Vitally?

Vitally is a Customer Success platform designed for B2B SaaS teams to manage accounts, track health, run projects, and coordinate customer communication. With Konnectify, you can automate updates between Vitally and your CRM, data warehouse, product analytics, or support tools—so your CS team always works from clean, timely data.

This integration supports both event-style polling triggers (for new/updated records) and a comprehensive set of write actions for core objects like Organizations, Accounts, Users, Tasks, Notes, and Custom Objects.

NEW TO VITALLY?

Set up your CS workspace

Create your Vitally instance and API key so Konnectify can read and write your customer data.

Visit Vitally →

NEW TO KONNECTIFY?

Build workflows in minutes

Connect apps, map fields, add logic, and automate customer-success operations without heavy engineering.

Create a Konnectify account →

What you can automate

• Create or update Organizations and keep traits current.

• Sync Accounts and pull health score breakdowns for reporting.

• Provision Users, manage associations, and support search lookups.

• Automate Tasks and Notes creation from external systems.

• Create Projects from templates when customers onboard or renew.

• Write back NPS responses, Messages, Conversations, and Custom Object instances.

API & Authentication

Authentication type: API Key (custom credentials)

This connector uses an API Key you generate in Vitally. In Konnectify, you’ll paste the key and select your Vitally data center region (US or EU). If you use the US data center, you’ll also provide your Vitally subdomain.

Supported API capabilities:

Read changes via polling triggers for Organizations, Accounts, Users, Notes, Projects, NPS Responses, and Tasks.
Create, update, fetch, and delete core objects (Organizations, Accounts, Users, Tasks, Notes, Messages, Conversations, NPS Responses).
Create Projects from templates and retrieve Account health score breakdowns.
Define and manage Custom Object schemas and instances, including search and deletion.

Plan & rate-limit note

Vitally API access, object availability (e.g., Custom Objects), and request limits can vary by plan and tenant configuration. If you hit rate limits, Konnectify will surface the API error; consider reducing polling frequency, narrowing workflows, or batching downstream operations where possible.

Official docs: Vitally API documentation (link provided for reference)

How to connect Vitally to Konnectify

Prerequisites

A Vitally account with permission to generate or access an API key.
Your Vitally Data Center Region (US or EU). For US, you’ll also need your subdomain.
A Konnectify workspace where you can create and activate workflows.

Add Vitally to a Workflow

Create a new workflow (or open an existing one) in Konnectify.
Select Vitally as your trigger app or action app.

Authorize via API Key

Paste your Vitally API Key into the connection form.
Select your Data Center Region (US or EU).
If you selected US, enter your subdomain (e.g., mycompany). For EU, leave it blank.

Configure the Trigger or Action

Choose the Vitally event you want to listen for (trigger) or the operation you want to perform (action).
Map fields from previous steps (e.g., external IDs, account IDs, message recipients).
For search actions, provide exactly one supported query parameter (as required by Vitally).

Important: Deletion actions are permanent in Vitally for several objects (Organizations, Accounts, Tasks, Notes, Messages, Conversations, NPS Responses, Custom Objects, and Custom Object Instances). Add safeguards like filters, approvals, or environment checks before enabling.

Test the Workflow

Run a test to fetch a recent trigger event (for polling triggers) or to execute the selected action.
Verify IDs and relationships (e.g., Account ↔ Organization, User ↔ Account) are mapped correctly.

Activate the Workflow

Turn on the workflow to start syncing changes continuously.
Monitor run history for errors and adjust mappings or filters as needed.

Triggers 19

Vitally triggers run as polling checks, meaning Konnectify periodically looks for newly created or recently updated records in Vitally.

Organizations 2 triggers

Organization Created

This trigger fires whenever a new Organization is created.

Organization Updated

This trigger fires whenever an existing Organization is modified.

Accounts 2 triggers

Account Created

This trigger fires whenever a new Account is created.

Account Updated

This trigger fires whenever an existing Account is modified.

Users 3 triggers

User Created

This trigger fires whenever a new User is created.

User Updated

This trigger fires whenever an existing User is modified.

User Deactivated

This trigger fires whenever an existing User is marked as deactivated.

Notes 3 triggers

Note Created

This trigger fires whenever a new Note is created.

Note Updated

This trigger fires whenever an existing Note is modified.

Note Archived

This trigger fires whenever an existing Note is marked as archived.

Projects 2 triggers

Project Created

This trigger fires whenever a new Project is created.

Project Updated

This trigger fires whenever an existing Project is modified.

NPS Responses 2 triggers

NPS Response Created

This trigger fires whenever a new NPS Response is created.

NPS Response Updated

This trigger fires whenever an existing NPS Response is modified.

Tasks 5 triggers

Task Created

This trigger fires whenever a new Task is created.

Task Updated

This trigger fires whenever an existing Task is modified.

Task Completed

This trigger fires whenever an existing Task is marked as completed.

Task Archived

This trigger fires whenever an existing Task is marked as archived.

Actions 36

Use Vitally actions to create, update, retrieve, search, and delete objects—plus manage messaging, conversations, and Custom Objects.

Organizations 4 actions

Create Organization

Creates an Organization with standard fields and dynamic custom traits.

Update Organization

Updates an Organization's standard fields and traits using its ID.

Get Organization

Fetches a specific Organization from Vitally using its ID or externalId.

Delete Organization

Permanently destroys the Organization record in Vitally, including all exclusively associated data.

Accounts 5 actions

Create Account

Creates an Account with standard fields and dynamic custom traits.

Update Account

Updates an Account's standard fields, organization link, and traits using its ID.

Get Account

Fetches a specific Account from Vitally using its ID or externalId.

Get Account Health Score Breakdown

Fetches the current Health Score breakdown for a specific Account in Vitally.

Delete Account

Permanently destroys the Account record in Vitally, including all exclusively associated data.

Users & Admins 6 actions

Create User

Creates a User with standard fields, associations, and dynamic custom traits.

Update User

Updates a User's standard fields, associations, and traits using its ID.

Get User

Fetches a specific User from Vitally using its ID or externalId.

Search Users

Searches for a User in Vitally using exactly one of the supported query parameters.

Delete User

Deletes a User immediately or schedules them for deletion in Vitally.

Search Admins

Searches for an Admin in Vitally using their email address.

Projects 3 actions

Create Project from Template

Creates a new Project assigned to an Account using an existing Project Template.

Update Project

Updates an existing Project's standard fields and traits using its ID.

Get Project

Fetches a specific Project from Vitally using its ID.

NPS Responses 4 actions

Create NPS Response

Creates a new NPS Response associated with a specific User.

Update NPS Response

Updates an existing NPS Response using its ID.

Get NPS Response

Fetches a specific NPS Response from Vitally using its ID.

Delete NPS Response

Permanently destroys the NPS Response record in Vitally.

Tasks 4 actions

Create Task

Creates a Task with standard fields, associations, and dynamic custom traits.

Update Task

Updates a Task's standard fields and traits using its ID.

Get Task

Fetches a specific Task from Vitally using its ID or externalId.

Delete Task

Permanently destroys the Task record in Vitally.

Notes 4 actions

Create Note

Creates a Note with standard fields, associations, and dynamic custom traits.

Update Note

Updates a Note's standard fields and traits using its ID.

Get Note

Fetches a specific Note from Vitally using its ID or externalId.

Delete Note

Permanently destroys the Note record in Vitally.

Messages 3 actions

Create Message

Creates a new Message. Supports adding recipients individually or via stringified JSON arrays.

Get Message

Fetches a specific Message from Vitally using its ID or externalId.

Delete Message

Permanently destroys the Message record in Vitally.

Conversations 4 actions

Create Conversation

Creates a new Conversation containing an initial message. Supports stringified nested arrays for complex recipient/message data.

Update Conversation

Updates an existing Conversation's standard properties and custom traits.

Get Conversation

Fetches a specific Conversation from Vitally using its ID or externalId.

Delete Conversation

Permanently destroys the Conversation record in Vitally.

Custom Objects 7 actions

Create Custom Object

Creates the schema definition for a new Custom Object and attaches associated Custom Fields.

Update Custom Object

Updates the schema definition (name, label, writeMode, customFields) of an existing Custom Object.

Get Custom Object

Fetches a specific Custom Object definition from Vitally using its ID.

Delete Custom Object

Permanently destroys the Custom Object schema definition in Vitally.

Create Custom Object Instance

Creates a new Instance for a specific Custom Object, including standard relationships and dynamic traits.

Update Custom Object Instance

Updates an existing Custom Object Instance using its ID or externalId.

Search Custom Object Instances

Searches for Instances using externalId, createdAt bounds, or limits.

Delete Custom Object Instance

Permanently destroys a specific Custom Object Instance record in Vitally.

Popular automations

Examples of common Vitally workflows you can build with Konnectify using the triggers and actions available in this connector.

Auto-create onboarding projects for new accounts

When a new Account appears in Vitally, automatically spin up a standardized onboarding Project from a template and assign it to the right team.

Account Created → Create Project from Template

Keep user profiles updated and searchable

When a User is updated in Vitally, you can validate key identity fields (like externalId/email) and update the corresponding record or notify your ops tools.

User Updated → Search Users → Update User

Create a CS task when an NPS response is received

When a new NPS Response is created, generate a follow-up Task in Vitally for your CSM, optionally enriched with the response details.

NPS Response Created → Create Task

Notify stakeholders when an organization changes

When an Organization is updated, automatically post an internal update by creating a Conversation (with an initial message) in Vitally to keep context centralized.

Organization Updated → Create Conversation

FAQ

How does authentication work for Vitally?

Vitally uses API Key authentication in this Konnectify connector. You’ll provide an API key plus your Vitally region (US/EU). If your tenant is in the US data center, you must also provide your Vitally subdomain.

Which Vitally plans are supported?

Any plan that includes API access can be connected. Availability of certain resources (for example, Custom Objects) may depend on your Vitally plan and tenant configuration. If an endpoint is unavailable, Konnectify will show the API error returned by Vitally.

Are Vitally triggers real-time?

Triggers in this connector are polling-based (not webhooks). Konnectify checks Vitally at an interval to find new or updated records. If you need faster reaction times, reduce the polling interval where available and filter workflows to minimize load.

How do I prevent duplicates (upsert behavior)?

This connector provides Create and Updateactions (no dedicated “Upsert” action). A common pattern is:

Use Get (by ID/externalId) or a Search action where available.
If found, run Update; otherwise run Create.

Ensure you consistently set and reuse externalId to make cross-system matching reliable.

What happens if we hit Vitally rate limits?

If Vitally returns a rate-limit response, the workflow run will record the error. To reduce rate-limit risk, lower polling frequency, add filters to reduce volume, and avoid unnecessary “Get” calls in tight loops. For high-volume use cases, consider consolidating writes (for example, only updating when key fields actually change).

Can I connect multiple Vitally accounts/tenants?

Yes. Create a separate Konnectify connection for each Vitally tenant (distinct API key/region/subdomain). Then select the appropriate connection in each workflow step to keep environments isolated (e.g., sandbox vs production).

How do Messages and Conversations handle recipients?

The Create Message action supports recipients either individually or via stringified JSON arrays. The Create Conversation action supports more complex, nested recipient/message structures (also as stringified nested arrays). If you’re generating recipient lists dynamically, validate your JSON formatting and ensure you’re using the correct Vitally IDs (User/Admin) expected by your workspace.

Ready to automate your Vitally workflows?

Connect Vitally to Konnectify to streamline Customer Success operations across your B2B SaaS stack.

Get started free →