Custify Make integrationAutomate Custify with Make.

A contact who signs up in another app gets a person record in Custify without anyone typing it, so health data and conversations attach to them from the first day.

Changes made elsewhere, a new job title in the CRM or a phone number from a form, flow into the existing Custify person so your team never works from stale details.

Pulling the full record of one known person lets later modules use every detail Custify holds about them, instead of the few values the trigger passed along.

Finding contacts by criteria, or listing them all, gives your scenario the people it should act on next: the ones to tag, update or notify.

Removing a person record from Custify keeps your account list clean when someone leaves a customer or asks to be erased from your tools.

Marking a person with a tag places them in the right segment automatically, so playbooks and filters in Custify pick them up without manual sorting.

Taking a tag off a person moves them out of a segment once the reason for it is gone, keeping your Custify lists honest.

A customer your scenario picks up from your CRM or billing tool gets its own account in Custify, ready for health scoring and onboarding.

Keeping company details in step with the rest of your stack means your team reads the same plan, owner or segment in Custify as everywhere else.

Loading one known company in full gives the next modules everything Custify stores about that account, beyond what the previous step passed on.

Looking up accounts by criteria, or listing every company, lets a scenario decide which customers it should work on before it writes anything.

All the contacts of one company come back together, which is what you need to reach everyone on an account instead of a single person.

Removing a company from Custify clears out accounts that should no longer be tracked, like test records or customers merged into another account.

Writing a note on a Custify record from another tool keeps the account history in one place: a call summary, a form answer or a sales remark.

Correcting or completing an existing note means the account keeps one clean record of a conversation instead of a trail of partial copies.

Reading every note back out of Custify lets you archive, analyze or share the history your team has built on its accounts.

New tags can be created by the scenario itself, so a segment exists in Custify before any person or company is placed into it.

Fetching one known tag confirms it exists and gives later modules its details, a small check that keeps tagging steps from failing.

Renaming or editing a tag in place keeps every person and company that carries it, which is easier than recreating the segment from scratch.

Pulling the full set of tags gives your scenario a map of the segments that exist in Custify, useful for syncing or cleanup.

Retiring a tag removes an outdated segment from Custify so your team stops filtering on labels that no longer mean anything.

Tagging an entity, the generic record type this module works on, lets you segment records beyond people from the same scenario.

Clearing a tag from an entity takes that record out of a segment when the condition behind it ends, without touching the tag itself.

Support requests from other channels can land in Custify as tickets, so success managers see open issues next to account health.

Changes to a support request, its status or details, carry into the matching Custify ticket so the account view stays accurate.

Removing a ticket keeps Custify free of test entries or requests that were logged by mistake and would distort the account picture.

Replies written elsewhere, an email answer or a chat message, join the ticket thread in Custify so the whole exchange sits in one place.

A to-do lands on the right person in Custify the moment something happens elsewhere, so follow-ups stop depending on memory.

Closing or editing a task from another tool keeps the Custify task list aligned with the work your team actually did.

Reading one known task in full brings its details into the scenario, ready for a reminder message or a status report.

Searching tasks by criteria, or listing all of them, lets you build digests, reminders or cleanups on top of your Custify task list.

This module reveals the filter values Custify accepts, which saves guesswork when you set up a search on tasks.

Activity from your product or other tools can be written into Custify as events, feeding the timeline your team reads before talking to a customer.

Grouping several calls into one batch request is the option for scenarios that already speak the Custify API and want to send work in one go.

Comments posted from a scenario put context straight onto the Custify record, where the account owner will see it during the next review.

Editing an existing comment lets a scenario correct or complete what it posted, keeping one comment per topic instead of a stack of versions.

Bringing all comments out of Custify gives you raw material for account reviews, exports or a search for the one to edit.

Opportunities spotted outside Custify, an upsell request or a renewal in the CRM, can be logged as deals on the account without retyping.

Stage or value changes flow into the matching Custify deal, so everyone reading the account sees where the opportunity really stands.

Reading every deal out of Custify gives you the material for a pipeline report or a sync with the tool where sales keeps its numbers.

Deleting a deal from Custify means an opportunity that was entered by mistake or duplicated no longer skews the pipeline your customer success team reads.

Writing each new invoice into Custify gives your account managers the billing history right next to the customer's health data instead of in a separate tool.

Correcting an invoice already stored in Custify keeps the amount or status your team sees in line with what your finance side actually says.

Every invoice Custify holds comes back, each one as its own bundle (one item passed to the next module), so you can loop over the whole billing history in a scenario.

Taking an invoice out of Custify is how you clean up a test invoice or one that was cancelled in your billing tool.

Recording each new subscription in Custify means the plan a customer pays for shows up where your team tracks renewals and churn risk.

Editing a subscription Custify already stores keeps the plan details your customer success managers rely on accurate after a change.

All the subscriptions stored in Custify come back one by one as bundles, ready to be filtered or sent to a spreadsheet.

Deleting a subscription record cleans up Custify when a plan was recorded by mistake or never went live.

Any endpoint of the Custify API becomes reachable with the connection you already set up, which covers what the listed modules do not.

Sending a file to Custify means a contract, a report or an onboarding document sits in the account your team works from.

Listing the files stored in Custify gives you one bundle per file, so the scenario can check what is already there or pass files along to another app.

Unlinking detaches an existing file in Custify, the move to make when a document no longer belongs where it was attached.

One module both creates a custom data object in Custify and updates it when it already exists, so your own data model stays in sync from one single module.

Deleting a custom data object keeps your custom records clean when the matching item disappears from your own system.