Custify

Custify + Konnectify

Custify Integration with Konnectify

Connect Custify to Konnectify to automate B2B SaaS customer success operations—sync people and companies, manage tickets and tasks, log notes and comments, and keep financial and time tracking records up to date.

People Companies Notes Tags Tickets Tasks Comments Files Events Surveys Time Tracks Meetings Health Scores Segments Lifecycles Playbooks Customer Objectives Financials 22 Triggers 43 Actions

ON THIS PAGE

→ What is Custify? → API & Authentication → How to connect → Triggers (22) → Actions (43) → Popular automations → FAQ

What is Custify ?

Custify is a customer success platform designed for B2B SaaS teams to manage accounts, stakeholders, health, tasks, notes, and customer interactions. By integrating Custify with Konnectify, you can keep customer data consistent across your stack, streamline support and success operations, and automatically log activity (tickets, comments, files, and time tracks) where your team works.

This connector supports automated workflows for both inbound signals (new/updated records) and outbound updates (create, update, upsert, and delete) across core Custify objects.

New to Custify?

Create an account and generate an API key to start syncing customer success data.

Visit Custify →

New to Konnectify?

Build workflows with triggers, actions, transformations, and branching—no heavy lifting required.

Create a Konnectify account →

What you can automate

• Create/update/upsert People and Companies (including custom fields)

• Sync Tickets and replies to keep support context visible in CS

• Log Notes, Comments, and Tasks to standardize customer touchpoints

• Manage Tags at scale (add/remove on People or other entities)

• Upload and manage Files attached to People or Companies

• Track financial items (deals, invoices, subscriptions) and time tracks

API & Authentication

Authentication method: API Key

This integration uses API Key authentication. When you connect Custify in Konnectify, you’ll be asked for your Custify API Key, which Konnectify uses to authenticate requests to the Custify API.

What the API key enables

Read changes via polling triggers (People, Notes, Tasks, Tickets, Files, and more)
Create, update, upsert, and delete records (People/Companies/Tags/Tickets/Tasks/Financials)
Attach operational context (Notes, Comments, Replies, Files, Time Tracks)

Recommended setup notes

Store the key securely and rotate it if it’s ever exposed
Use Upsert actions to prevent duplicates
For delete operations, confirm GDPR/“forget me” implications before enabling

Important: plan restrictions & rate limits

Custify API availability and limits can vary by plan and account settings. If you see intermittent failures or delayed trigger pickups, reduce polling frequency, add filtering, and avoid large bursts of write actions (for example, mass tag updates or financial upserts).

API reference: Custify API base URL & documentation (verify endpoints and required fields in your Custify account documentation).

How to connect Custify to Konnectify

Prerequisites

An active Custify account with API access enabled
Your Custify API Key
A Konnectify workspace with permission to create workflows and connections

Add Custify to a Workflow

Create a new Workflow in Konnectify (or open an existing one).
Click Add step and select Custify.

Authorize via API Key authentication

When prompted, paste your Custify API Key into the connection field.
Name the connection (useful when you manage multiple Custify environments).

Configure the Trigger or Action

Select a trigger (e.g., Person Updated) or an action (e.g., Upsert Company).
Map fields from previous steps into Custify fields (including custom fields where supported).

Watch out: For updates and deletes, make sure you use the correct identifier (internal ID vs external IDs such as externalId, user_id, or email). A wrong ID can overwrite or remove the wrong record.

Test the Workflow

Run a test using known records in Custify (or create a test Person/Company).
Verify field mapping, IDs, and expected changes in Custify.

Activate the Workflow

Turn on the workflow.
Monitor the first few runs and adjust mappings/filters if needed.

Triggers 22

Custify provides 22 polling triggers in Konnectify. Polling triggers check Custify at regular intervals and fire when new or updated records are detected.

People 2 triggers

Person Created

This trigger fires whenever a new Person is created.

Person Updated

This trigger fires whenever an existing Person is modified.

Notes 2 triggers

Note Created

This trigger fires whenever a new Note is created.

Note Updated

This trigger fires whenever an existing Note is modified.

Tasks 2 triggers

Task Created

This trigger fires whenever a new Task is created.

Task Updated

This trigger fires whenever an existing Task is modified.

Tickets 2 triggers

Ticket Created

This trigger fires whenever a new Ticket is created.

Ticket Updated

This trigger fires whenever an existing Ticket is modified.

Files 1 triggers

File Created

This trigger fires whenever a new File is uploaded and attached to a Company or Person.

Surveys 1 triggers

Survey Created

This trigger fires whenever a new Survey is created.

Time Tracks 2 triggers

Time Track Created

This trigger fires whenever a new Time Track is created.

Time Track Updated

This trigger fires whenever an existing Time Track is modified.

Meetings 2 triggers

Meeting Created

This trigger fires whenever a new Meeting is created.

Meeting Updated

This trigger fires whenever an existing Meeting is modified.

Health Scores 2 triggers

Health Score Created

This trigger fires whenever a new Health Score is created.

Health Score Updated

This trigger fires whenever an existing Health Score is modified.

Segments 2 triggers

Segment Created

This trigger fires whenever a new Segment is created.

Segment Updated

This trigger fires whenever an existing Segment is modified.

Lifecycles 2 triggers

Lifecycle Created

This trigger fires whenever a new Lifecycle is created.

Lifecycle Updated

This trigger fires whenever an existing Lifecycle is modified.

Playbooks 2 triggers

Playbook Created

This trigger fires whenever a new Playbook is created.

Playbook Updated

This trigger fires whenever an existing Playbook is modified.

Customer Objectives 2 triggers

Customer Objective Created

This trigger fires whenever a new Customer Objective is created.

Customer Objective Updated

This trigger fires whenever an existing Customer Objective is modified.

Actions 43

Use actions to create, update, upsert, fetch, and delete Custify records—plus operational actions like replying to tickets, uploading files, and tracking financial objects.

People 7 actions

Create Person

Creates a new person profile in your Custify account.

Update Person

Updates an existing person's details in Custify.

Upsert Person

Upserts a person in Custify using internal ID, user_id, or email.

Get Person

Fetches a person's details from Custify using their internal ID, user_id, or email.

Delete Person

Deletes a person and all associated data from Custify. This represents GDPR compliance ('forget me').

Add/Remove Tag

Adds or removes a specific tag for the provided people in Custify.

Insert Event

Submit events via a POST method to https://api.custify.com/event, which accepts a JSON object describing the event.

Companies 5 actions

Create Company

Creates a new company profile in your Custify account.

Update Company

Updates an existing company's details in Custify.

Upsert Company

Upserts a company in Custify using internal ID or company_id.

Get Company

Fetches a company's details from Custify using its internal ID or company_id.

Delete Company

Deletes a company and all associated data from Custify. This represents GDPR compliance ('forget me').

Notes 3 actions

Create Note

Creates a new note associated with a Company or Person in Custify.

Update Note

Updates an existing note's details by sending a POST request to the note's Custify internal ID.

Upsert Note

Upserts a note in Custify. If an ID is provided, it updates the note; otherwise, it creates a new one.

Tags 5 actions

Create Tag

Creates a new tag by sending a POST request.

Update Tag

Updates an existing tag by sending a POST request to its Custify internal ID.

Upsert Tag

Upserts a tag in Custify. If an ID is provided, it updates the tag; otherwise, it creates a new one.

Delete Tag

Tags can be deleted by sending a DELETE request to the entry's URL using the Custify id. Note that this function permanently deletes the corresponding tag set on people.

Add/Remove Tag from Entity

Tags can be added/removed to/from multiple entities of the same category by sending a PATCH request.

Scores 2 actions

Assign NPS Score

You can assign an NPS score to a person by sending a POST request to https://api.custify.com/nps_score/{entity}.

Assign CSAT Score

You can assign a CSAT score to a person by sending a POST request to https://api.custify.com/csat_score/{entity}.

Tickets 4 actions

Create Ticket

Create a new ticket on Companies or People.

Update Ticket

Update an existing ticket based on the externalId for the ticket. Works as a patch, only provided fields are saved.

Delete Ticket

Delete an existing ticket based on the externalId for the ticket

Reply To Ticket

Add a new reply to an existing ticket based on the externalId.

Tasks 2 actions

Create Task

Create a new task on Companies or People.

Update Task

Update an existing task. You can send only the data that changes by providing the Custify internal ID `_id` of the existing task.

Comments 3 actions

Create Comment

You can create a new comment by sending a POST request to https://api.custify.com/comment/{entityModel}/{entity}.

Update Comment

You can update an existing comment by sending a POST request to https://api.custify.com/comment/{entityModel}/{entity} with the comment ID.

Upsert Comment

Upserts a comment. If an ID is provided, it updates the existing comment; otherwise, it creates a new one.

Files 3 actions

Upload File

Upload a file to a Company or a People by sending a POST request to https://api.custify.com/file. The request uses multipart/form-data.

Unlink File

You can unlink a file from a Company or a People by sending a POST request to https://api.custify.com/file/unlink.

Enable/Disable File in Portal

Enable or disable a file to be shown in the portal by sending a PUT request to https://api.custify.com/file/:id/showInPortal.

Financials 12 actions

Create Financial Deal

You can create/update financial deals by sending a POST request to https://api.custify.com/financial/deal that has in the body the field externalId.

Update Financial Deal

Update an existing financial deal by sending a POST request to https://api.custify.com/financial/deal/{entity} or using externalId in the body.

Upsert Financial Deal

Upserts a financial deal. If found via entity ID or externalId, it updates the record; otherwise, it creates a new one.

Delete Financial Deal

Delete an existing financial deal based on the externalId for the financial deal (in the query params) or the entity in the params of the request.

Create Financial Invoice

You can create/update financial invoices by sending a POST request to https://api.custify.com/financial/invoice that has in the body the field externalId.

Update Financial Invoice

Update an existing financial invoice by sending a POST request to https://api.custify.com/financial/invoice/{entity} or using externalId in the body.

Upsert Financial Invoice

Upserts a financial invoice. If found via entity ID or externalId, it updates the record; otherwise, it creates a new one.

Delete Financial Invoice

Delete an existing financial invoice based on the externalId for the financial invoice (in the query params) or the entity in the params of the request.

Create Financial Subscription

You can create/update financial subscriptions by sending a POST request to https://api.custify.com/financial/subscription that has in the body the field externalId.

Update Financial Subscription

Update an existing financial subscription by sending a POST request to https://api.custify.com/financial/subscription/{entity} or using externalId in the body.

Upsert Financial Subscription

Upserts a financial subscription. If found via entity ID or externalId, it updates the record; otherwise, it creates a new one.

Delete Financial Subscription

Delete an existing financial subscription based on the externalId for the financial subscription (in the query params) or the entity in the params of the request.

Time Tracks 3 actions

Create Time Track

Create a new time track on Companies or People.

Update Time Track

Update an existing time track on Companies or People.

Delete Time Track

Delete an existing time track based on the Custify internal ID (in the query params).

Popular automations

Here are a few proven workflow ideas you can build quickly with the available Custify triggers and actions.

Enrich People automatically when they change

When a person is updated in Custify (or via another system), fetch their latest details and standardize tags for segmentation.

Person Updated → Get Person → Add/Remove Tag

Create a follow-up task when a ticket is created

Ensure every new support issue creates a success follow-up task linked to the same customer context.

Ticket Created → Create Task → Create Note

Keep company records synced using upserts

When a person is created, upsert the matching company and upsert the person to ensure clean data and avoid duplicates.

Person Created → Upsert Company → Upsert Person

Automatically publish uploaded files to the customer portal (when appropriate)

When a file is added to a customer record, enable visibility in the portal or link/unlink based on your internal rules.

File Created → Enable/Disable File in Portal

FAQ

How does authentication work for Custify in Konnectify?

Custify uses API Key authentication. You provide your Custify API Key when creating a connection, and Konnectify uses it to authorize API requests on your behalf.

Which Custify plans are supported?

Any plan that includes Custify API access should work. If an endpoint returns authorization errors, confirm your plan and API permissions with Custify support or your admin.

Are Custify triggers real-time?

Not currently. All available triggers are polling triggers, meaning Konnectify checks Custify on an interval and emits events when it detects new or changed records. This can introduce a small delay compared to webhooks.

How can I prevent duplicate People/Companies in Custify?

Use the Upsert Person and Upsert Company actions whenever possible. Upserts let you match existing records using stable identifiers (for example, internal ID, user_id, email, or company_id) and only create a new record if no match exists.

What happens if Custify rate limits my requests?

If Custify responds with rate-limit errors, Konnectify workflows may retry depending on your workflow configuration. To reduce rate pressure, limit parallelism, add filters to triggers, and consolidate writes (for example, prefer a single upsert over multiple updates).

Can I connect multiple Custify accounts (e.g., staging + production)?

Yes. Create multiple Custify connections in Konnectify (one per API key/account). Use clear connection names like Custify Prod and Custify Staging to avoid mistakes when building workflows.

What identifiers should I use for Tickets and Financial objects?

For Tickets, updates/deletes/replies are performed using the ticket’s externalId. For Financial Deals/Invoices/Subscriptions, Custify commonly uses externalId (and sometimes an entity ID) for updates and deletes. Standardize these IDs in your source system to ensure consistent sync behavior.

Ready to automate your Custify workflows?

Connect Custify to Konnectify and keep your customer success operations in sync—end to end.

Get started free →