Tendro integrations push the leads you capture at events directly into your CRM or marketing automation platform, so the contacts are immediately available for follow-up workflows, attribution reporting, and campaign enrollment.

In practical terms, when a scanner in your booth takes a photo of a badge, the lead is created in Tendro, enriched in the background, and — if an integration is configured — synced to your downstream system as a contact record with the fields you've mapped.

This guide walks through the integrations workflow end-to-end: activating integrations on your workspace, connecting a CRM, mapping fields, transforming values, and the special handling for the event name.

HubSpot as the worked example Tendro connects natively to HubSpot and Salesforce. Other CRMs and tools, such as Marketo, Pardot, Pipedrive and Zoho, get a connector built on request. The general flow — Connect, then Configure Field Mapping — is the same across all of them. This guide uses HubSpot as the worked example throughout; the screenshots and field references will look slightly different on other platforms, but the steps and concepts apply.

Integrations is the last item in the left navigation of the Tendro web platform. It shows every available integration as a tile, with its current connection state ("Connected" or "Not Connected") shown in the top-right of each tile.

HubSpot sync comes with every paid event. On a new workspace it turns on with your first paid event. Until then the Integrations page shows it as locked. Leads sync from paid events. Before you connect a CRM, confirm your email address from the link Tendro sent you. On older plans, ask support (Need Help? at the bottom of the left navigation) to turn integrations on.

Connecting an integration links your Tendro workspace to your CRM or marketing automation account using OAuth. Tendro never sees or stores your CRM password, authentication happens on the CRM's own login page.

1. Open Integrations in the left navigation.

2. Find the tile for the platform you want to connect (e.g. HubSpot).

3. Click the Connect button on that tile.

4. Your browser will open the CRM's OAuth authorisation page in the same tab. Sign in to the CRM if you are not already signed in.

5. Choose the specific account or instance you want to connect to. Most CRMs allow a single user to have access to several accounts — make sure you pick the right one.

6. Click Choose Account (or the equivalent confirmation button) to grant Tendro access.

7. You will be redirected back to the Tendro Integrations page, where the tile will now show Connected.

What permissions does Tendro request? For HubSpot, Tendro asks to write contacts, to read your contact property settings, and to read owners. Writing contacts lets it create and update contacts and add a Note to each one. Reading property settings fills the field mapping list. Reading owners lets it set the contact owner. On Sales Hub Professional or Enterprise it also asks, as optional permissions, to write Leads and to read Lead properties for field mapping. Tendro does not ask to read your contact records, deals or companies.

When the connection completes, Tendro syncs name, email, phone, company and job title with no setup. It sets the contact owner to the rep the lead is assigned to, or else the rep who captured it, when that person's email matches a HubSpot user. When a rep adds notes or answers qualifying questions, Tendro adds them as one Note on the contact, headed with the event name. On Sales Hub Professional or Enterprise it also creates a HubSpot Lead linked to the contact. Everything else is set up in Field Mapping (section 3).

Once an integration is connected, the tile's Connect button is replaced by a Manage dropdown. Clicking Manage exposes three actions:

Field mapping defines, for each connected integration, which Tendro field flows into which CRM field. Name, email, phone, company and job title sync by default. Everything else, including the event name, LinkedIn URL, enrichment data and your custom tags, is opt-in: you add rows to the field mapping panel.

Go to Integrations → click Manage on the connected tile → Configure Field Mapping.

The left-hand dropdown lists every field Tendro can output:

1. Click + Add Field Mapping at the bottom of the panel. A new empty row appears.

2. In the left dropdown, choose the Tendro field you want to sync.

3. In the right dropdown, choose the CRM field that should receive it. CRM fields are listed with their object namespace shown in brackets (e.g. [contact]).

4. Repeat for every field you want to sync.

5. Click Save Mappings.

CRM fields must exist first. Tendro will not create new fields in your CRM for you. If you want to sync a custom tag to HubSpot, you must first create a matching property in HubSpot (Settings → Properties → Create property), then return to Tendro and select it in the field mapping dropdown. The same is true for Salesforce, Marketo, and the other integrations.

In general, text fields map to text fields, numbers to numbers, and so on. Tendro and the connected CRM do not need to use identical field types for every mapping — you can do some cross-type mapping (for example, a Tendro dropdown can often map to a CRM text field). However, the matrix of which conversions work is not exhaustively documented, so when in doubt, test with a single lead and verify the value arrives correctly in the CRM.

To remove a mapped field, click the trash icon at the right end of the row. To change which Tendro or CRM field is mapped, use the dropdowns directly. Click Save Mappings to apply your changes.

Field mapping pairs two fields together. Value mapping goes one level deeper: it lets you translate the actual values stored in those fields. This is for cases where Tendro and the CRM use different codes or labels for the same concept.

Common scenarios:

Each field mapping row has a small cog icon to the right of the field selectors. Click it to open the Map Field Values dialog for that specific field mapping. From there:

1. Note the Tendro Field and CRM Field shown at the top of the dialog — these confirm which mapping you are editing.

2. In Add Value Mapping, the left dropdown (Tendro Value) lists the options defined for that Tendro field. Pick the one you want to translate.

3. In the right text box (CRM Value), type the value as it should appear on the CRM side.

4. Click + Add Mapping to commit that pair. Repeat for each value pair.

5. If you leave the value mappings empty, values sync as-is — Tendro will write whatever the Tendro field contains directly to the CRM.

6. Click Save Mappings on the parent panel when done.

Tip Value mapping is what powers territory routing: map the value into a property, and let a HubSpot workflow assign the owner. If your follow-up workflow depends on a CRM field having one specific set of values, configure the mapping at the integration layer rather than asking scanners to remember the exact CRM-side codes.

Almost every customer wants to know which event each contact came from — for attribution, for enrolling the contact in an event-specific nurture sequence, or simply for reporting. There are two ways the event name can flow into your CRM, and which one applies to your workspace depends on when it was configured.

Every Note Tendro adds is headed with the event name. To report by show, map Tendro's Event Name field to a HubSpot property in Field Mapping. On Sales Hub Professional or Enterprise, map it on the HubSpot Lead: each show gets its own Lead, so each keeps its own event name. Mapped to the contact, the property holds the event from the most recent sync.

Before Event Name was in the mapping list, customers used a manual workaround: create a custom tag in Tendro called something like "Event", set its default value to the name of the event for which you are scanning, and map it to a CRM field through Field Mapping (section 3).

The downside of this approach is that you have to remember to set the default tag value for every new event, and a missed default means the leads from that event are not attributed correctly. Mapping Event Name removes that risk.

If you currently have a legacy event tag set up and now map Event Name, you can safely retire the tag — but coordinate with your CRM admin first, since downstream reports and workflows may still be filtering on the old tag-based property.

A common reason for connecting an integration is to drive automated follow-up the moment a lead is scanned. The full pattern works like this:

1. At the booth, the scanner takes a photo of a badge or business card.

2. Tendro creates the lead, enriches it (LinkedIn, company info, keywords) in the background, and applies any custom tags the scanner selected at scan time.

3. Tendro pushes the lead to HubSpot shortly after capture (or once the phone is back online), with your mapped fields filled in.

4. A HubSpot workflow watches for contacts with your mapped event property and enrols them in an event-specific sequence, sends collateral, books a meeting, or whatever fits your motion.

5. Your follow-up can be on its way before the visitor reaches the next booth.

Tag-driven workflow branching Custom Tendro tags are particularly useful for branching the follow-up workflow at the booth. For example, define a Tendro tag called "Interest" with options "Wants meeting", "Wants collateral", "Just browsing". Map it to a CRM property. Then build three CRM workflows — one per option — that send the right material automatically. The scanner just picks the right option in the app; the rest happens without them.

Tendro has its own dashboard for slicing leads by event, user, and tag. Most teams that have a fully configured CRM integration end up doing their reporting in the CRM rather than in Tendro, because that is where their existing workflows, deal data, and revenue attribution live.

In practice, expect to use the Tendro dashboard for at-event monitoring (how many leads has each scanner captured today?) and to lean on the CRM for after-event attribution and pipeline reporting.

If something is not behaving as expected, the fastest channels are:

Feedback on the product — Tendro is actively developed and welcomes input. If something in the app would be more useful with a particular change, share it. Note that not every request will be implemented — Tendro intentionally keeps the app simple, since complexity tends to reduce in-the-field usage.