A CRM is only as useful as the data that reaches it. Gartner defines customer relationship management as a business strategy that optimises profitability and customer satisfaction by organising around customer segments and fostering customer-centric behaviours[reference:0]. That definition assumes the data exists. In most organisations, the moment a professional meets a new contact, the data exists — but it lives in a pocket. It is on a paper card, in a phone’s address book, or in a personal spreadsheet that the company cannot see. The contact is real; the record is not.
This is the gap that CRM integration for digital business cards is meant to close, and it is worth being precise about how narrow that gap actually is. Signify’s CRM integration connects an organisation’s collected contacts to Zoho CRM or HubSpot, and it does so in a specific, one-directional way. It is not a universal API, it does not support every CRM, and it does not run continuously in the background. Those limits matter, because the marketing language around “integrations” usually implies more than the product delivers. This guide sets out what the integration actually does, what it does not do, and when it is worth turning on.
- Signify’s CRM integration supports Zoho CRM and HubSpot — not Salesforce, and not a broad app marketplace.
- The sync is one-way from Signify to the CRM. Changes made in the CRM are not automatically brought back into Signify[reference:1].
- Each CRM connection is independent: connecting Zoho does not connect HubSpot, and each has its own sync controls[reference:2].
- Team admins can also export leads as CSV or Excel if the CRM integration is not the right fit[reference:3].
The problem: contacts trapped in individual pockets
A team of ten people, each meeting five new contacts a week, produces roughly 200 new professional relationships a month. If those contacts are captured on paper cards and typed into individual phones, the company has almost no visibility into any of them. The data exists in fragments — a name in one person’s address book, a note in another person’s notebook, a follow-up that one person remembers and another does not. When a salesperson leaves, the relationships leave with them.
The Harvard Business Review has documented how often the follow-up step is skipped in professional networking, and the pattern is structural rather than personal: the data needed for the follow-up is scattered across surfaces that do not talk to each other. A CRM does not fix that on its own. It only fixes it if the data actually reaches it.
A Signify digital business card changes where the contact is captured — a shared profile rather than a paper object — and the leads integration is the part that moves the captured contact from Signify into the CRM. For a team on Signify Teams, that is where the value of the integration sits: not in the card itself, but in the fact that the card’s contacts stop being personal and start being organisational.
What the integration actually does
The verified capability set is small and specific. Each of the four items below is documented in Signify’s own CRM integration guide, which is the authoritative source on how the feature behaves.
Connect Zoho CRM or HubSpot, independently
Signify’s organisation CRM integration page has a separate connection card for Zoho CRM and for HubSpot. You can connect either one or both, but connecting one does not connect the other. Each card has its own status (Not connected, Connected) and its own authorization flow[reference:4].
Sync contacts individually or in bulk
Once a CRM is connected, contacts collected through the team’s digital cards can be sent to that CRM one at a time, or in bulk using the Sync all control. The bulk action applies only to the provider whose connection card you are using — Sync all on the Zoho card does not push contacts to HubSpot[reference:5].
Re-sync when contact details change
If a contact’s details are updated in Signify, the integration supports re-syncing the updated record to the connected CRM. That matters for a team whose contacts change roles and companies — the CRM record can be kept aligned with the current version rather than the version captured at the event[reference:6].
Disconnect without deleting records
Removing a CRM connection from Signify does not delete the records that have already been sent to the CRM. The disconnect action removes the connection itself, not the historical data. That is the right behaviour for a team that is switching CRMs — the historical records stay where they were sent[reference:7].
There is one more verified path that is often more useful than the CRM integration for a smaller team: CSV or Excel export. Team admins can export all contacts collected by the team as a spreadsheet[reference:8]. For a team that does not use Zoho or HubSpot, that export is the practical way to get the data into whatever system they do use, without requiring an integration that does not exist.
What it does not do
This is the section most integration articles skip, and it is the reason many buyers end up disappointed. The verified limits below are not criticisms — they are the scope of the feature as documented, and knowing them is what lets you decide whether the feature fits your workflow.
No Salesforce support
The documented CRM connections are Zoho CRM and HubSpot. If your organisation runs Salesforce, the integration as currently documented does not cover it. The CSV export is the workaround[reference:9].
No two-way sync
The integration is initiated from Signify. Changes made in Zoho or HubSpot are not automatically brought back into Signify[reference:10]. If a contact’s email is updated in the CRM, that change does not propagate to the card.
No continuous background sync
Syncing is an action a team member or admin triggers, not a live pipeline. New contacts do not appear in the CRM automatically the moment they are captured — someone has to run the sync[reference:11].
No public REST API for custom builds
There is no publicly documented developer API for Signify.ink that would let a team build a custom integration with a different CRM. The documented paths are the Zoho/HubSpot integration and the CSV export.
Integration vs CSV export vs nothing
A team has three realistic options for getting contact data out of the card and into a system of record. They are not equally good, and the right one depends on the team’s size and the CRM it already uses.
| Dimension | CRM integration | CSV / Excel export | No export (paper or personal phone) |
|---|---|---|---|
| Supported destinations | Zoho CRM, HubSpot | Any system that imports a spreadsheet | None |
| Direction | Signify → CRM only | One-time export | N/A |
| Trigger | Manual or Sync all | Manual | N/A |
| Re-sync on update | Yes, for connected contacts | Re-export required | No |
| Company owns the data | Yes, in the CRM | Yes, in the spreadsheet | No — it lives with the individual |
| Best for | Teams already on Zoho or HubSpot | Teams on any other CRM or none | Nobody, once the team has more than a few people |
The “no export” column is the default for most teams before they adopt a digital card, and it is the one that quietly costs the most. The American Bar Association and UPrinting both cite the widely used figure that roughly 88% of paper business cards are thrown away within a week — and the 12% that survive are usually in a drawer, not a CRM.
Sources: Signify CRM integration guide (Zoho CRM and HubSpot); American Bar Association and UPrinting (88%).
When it is worth turning on
The integration is not worth configuring for every team. It is worth configuring when three conditions are true at once, and none of them is satisfied by a solo professional.
-
The team already runs Zoho CRM or HubSpot. If the organisation uses a different CRM, the integration is not the path — the CSV export is. Check which CRM the team actually uses before assuming the integration applies.
-
More than three people collect contacts. Below that threshold, a shared spreadsheet is a reasonable interim, and the overhead of configuring OAuth connections is not worth the setup time. Above it, the spreadsheet becomes a data silo of its own.
-
The team has a process for what happens after the sync. Moving a contact into the CRM is not the outcome — it is the start of the follow-up. If nobody owns the follow-up sequence, the integration just relocates the data from one unused surface to another.
-
The organisation wants the data to survive staff turnover. This is the strongest case. A CRM record that lives at the company level survives a salesperson leaving; a phone contact does not. The integration is what makes the contact a company asset rather than an individual one.
-
The team is willing to run the sync. Because the sync is action-triggered rather than continuous, someone has to own the habit of running it — after an event, at the end of the week, or on a schedule the team agrees on. A sync nobody runs is not a sync.
For a team that meets all five, the integration is genuinely useful. For a team that meets only one or two, the CSV export or a well-run shared spreadsheet is usually the better interim. The Signify Teams pricing page and the Teams feature overview cover the seat tiers and the roles (Owner, Admin, Manager, Member) that determine who can run the sync.
What to verify before you deploy
If you are evaluating the integration for an organisation, these are the specific things to confirm before you commit. Each one is a place where an assumption can go wrong.
-
Confirm which CRM the team uses. Zoho CRM and HubSpot are supported. Salesforce and other CRMs are not, as of the documented integration. Do not assume broad CRM coverage.
-
Confirm who has permission to authorise the connection. The person connecting Signify to the CRM needs permission to approve access to the organisation’s CRM account. That is usually an admin, not a team member.
-
Decide whether you need one CRM or both. Connecting Zoho does not connect HubSpot. If the team uses both, each needs to be connected and each has its own sync controls.
-
Plan for the one-way limitation. If someone updates a contact in the CRM, that change will not flow back into Signify. Decide who owns the Signify record and who owns the CRM record so the two do not drift.
-
Test the CSV export as a fallback. Even if you plan to use the integration, confirming that the export works is a useful safety net for a one-off migration or a CRM change. Team admins can export leads as CSV or Excel[reference:12].
-
Check the enterprise options if you need white-label. White-label options are available for enterprise customers, and enterprise plans include a dedicated account manager and priority support[reference:13]. If the integration is part of a larger deployment, the company page and the Consac help desk are the places to confirm the specifics.
Frequently asked questions
Which CRM systems does Signify integrate with?
Zoho CRM and HubSpot, as documented in Signify’s CRM integration guide. Salesforce is not currently supported by the documented integration. Teams using a different CRM can use the CSV or Excel export as a manual path.
Is the sync two-way?
No. The integration is initiated from Signify, and changes made in Zoho CRM or HubSpot are not automatically brought back into Signify[reference:14]. If a contact’s details are updated in the CRM, the Signify record does not change unless someone updates it separately.
Does syncing to Zoho also sync to HubSpot?
No. Each CRM has its own connection card and its own sync controls. Connecting Zoho does not connect HubSpot, and the Sync all action on one card applies only to that provider[reference:15].
What happens if I disconnect a CRM?
The connection is removed, but records already sent to the CRM are not deleted. The disconnect action removes the link between Signify and the CRM, not the historical data in the CRM[reference:16].
Can I export contacts without a CRM integration?
Yes. Team admins can export all contacts collected by the team as a CSV or Excel file[reference:17]. That is the practical path for a team whose CRM is not Zoho or HubSpot, or for a one-off migration.
Is there a public API I can use to build a custom integration?
There is no publicly documented developer API for Signify.ink that would support a custom integration with another CRM. The documented paths are the Zoho/HubSpot integration and the CSV export. If a custom build is a hard requirement, that is a question to raise with the enterprise team before committing to the platform.
Does the integration work for individual cards, or only for teams?
The CRM integration is managed from the organisation workspace, so it is a Signify Teams feature. A solo professional on an individual card does not have an organisation workspace to connect a CRM to; the pricing page covers the tiers.
How do I get started?
Set up a team on Signify Teams, open the organisation CRM integration page, connect Zoho CRM or HubSpot (or both), and use the Sync all control or individual sync actions to send eligible contacts. The leads integration page is the product overview.
Move the contact out of the pocket
Zoho CRM or HubSpot, one direction, action-triggered — the honest scope of what the integration does, and why it is still worth turning on for a team.
Set up Signify Teams