Use ready-made lead-broker integrations

If you buy leads from a broker (Wattfox, Aroundhome, DAA, Eza ("Einfach zum Angebot"), Interlead, or Bitrix), Reonic ships a ready-made integration for each. Once connected, broker leads flow straight into your Requests kanban with full contact details, the broker's lead ID stamped on the request, and your existing CRM and AI scoring kicking in automatically. No manual copy-paste, no CSV export-import: the broker sends, you respond.

Before you start

• You need Admin role on your workspace to configure lead-broker integrations.
• You need an active contract with the broker. The integration ferries leads; the commercial relationship is separate. Sign with Wattfox, Aroundhome, DAA, Eza, Interlead, or Bitrix first.
• You need API credentials from the broker, typically an API key or OAuth credentials (the exact shape varies per broker, see below).
• Decide your lead-source taxonomy. Broker leads can be auto-tagged with a specific lead source for cleaner reporting. Set up the lead source first if you want auto-attribution. See Lead sources for the lead-source list.

Which brokers Reonic ships integrations for

Reonic ships ready-made integrations for these inbound lead brokers:

• **Aroundhome** — High-volume German home-improvement lead marketplace — DE — API key
• **Wattfox** — German PV / heat-pump lead broker with distribution channels — DE — OAuth (username plus password to access token)
• **DAA** — German renewable-energy lead network — DE — Username plus API key
• **Eza ("Einfach zum Angebot")** — German PV / heat-pump comparison portal — DE — OAuth access token
• **Interlead** — Multi-vertical lead network — DE/EU — API key
• **Bitrix** — Dual-purpose: inbound broker plus outbound CRM — DE/EU — OAuth app token

Each is a separately-installable module. You can connect any combination, whether that's one, two, or several at once.

Pro tip: If your broker isn't in the list above, your account manager can scope a custom integration. As a quick alternative, every broker that exports CSV or Excel can be ingested via the Excel import, or, if it generates per-lead emails, by forwarding those into Reonic.

Open the integrations settings

1. Click Settings in the left sidebar.
2. Go to Company settings > Integrations.
3. Find the broker you want to connect.

Connect Wattfox

1. Click Connect (or Configure) on the Wattfox row.
2. Fill in the Wattfox API ID / username (provided by Wattfox), the Wattfox password / API key, and the distribution channel ID. Wattfox uses per-channel scoping; one workspace can pull from multiple channels by setting up multiple connections or by switching the channel ID.
3. Save. Reonic begins bringing in leads on Wattfox's cadence.
4. Inbound leads appear in your Requests kanban tagged as Wattfox, with the broker's lead ID stamped on each row.

Pro tip: Wattfox's distribution channel is the unit of attribution. If you buy leads through multiple channels (PV-only, heat-pump-only, regional), set up one connection per channel or rotate the channel ID, and your reporting stays cleaner.

Connect Aroundhome

1. Click Connect on the Aroundhome row.
2. Fill in the Aroundhome API key and any additional broker-side identifiers (distribution channel, package code) Aroundhome provides.
3. Save.
4. Aroundhome leads flow in tagged as Aroundhome, with the broker's lead ID stamped on each request.

Pro tip: Brokers often sell leads in several packages or channels that convert differently. Tag each package as its own lead source, and you'll quickly see which ones convert and which don't.

Connect DAA

1. Click Connect on the DAA row.
2. Fill in the DAA username and DAA API key.
3. Save.
4. DAA leads arrive on DAA's cadence, tagged as DAA, with the broker's lead ID stamped on each lead.

Connect Einfach zum Angebot (Eza)

1. Click Connect on the Eza row.
2. Fill in the OAuth credentials Eza provided.
3. Save.
4. On each sync, new Eza leads since the last one flow in tagged as Eza.

Connect Interlead

1. Click Connect on the Interlead row.
2. Fill in your Interlead API key.
3. Save.
4. Interlead leads arrive on the broker's cadence tagged as Interlead, with the broker's lead ID stamped on each row.

Connect Bitrix as an inbound broker

Bitrix is both an inbound broker (it sends new leads to Reonic) and an outbound CRM (it receives requests you create directly in Reonic). You can use either or both.

1. Click Connect on the Bitrix row.
2. Fill in the Bitrix OAuth app token and the portal URL.
3. Set sync lead scope to Lead (Bitrix sends leads to Reonic, inbound), Deal (Reonic sends deals to Bitrix, outbound, the default), or None (credentials stay in place while sync pauses).
4. Save.

Pro tip: If you use Bitrix for everything (CRM plus lead source), set sync lead scope to Lead or Deal based on which direction matters more; you run one direction at a time. You can keep Bitrix as your outbound CRM and use one of the other brokers (Wattfox, Aroundhome) for inbound leads.

What happens after you connect

Once a broker is connected:

1. Reonic brings in leads on the broker's cadence. Some brokers deliver instantly; others deliver on their own schedule, typically a few times per day.
2. Each inbound lead becomes a Request in your kanban. The Request carries all the contact info the broker provided (name, email, phone, address), any property data the broker captured (consumption, building type, requested package), the broker's lead ID (so re-imports from the same broker are recognized), and a source tag matching the broker for filtering and reporting.
3. Your other integrations run automatically. Inbound broker leads trigger the same follow-on actions as a manually-created request, so your outbound CRM (HubSpot, Pipedrive, Salesforce, Weclapp, Bitrix-deal) receives the lead automatically, AI Lead Score runs on the lead, the welcome email fires (if configured), and so on.
4. You work the lead in Reonic. From your kanban: qualify, create an offer, sign, hand off to installation, all the standard Request lifecycle.

Tag broker leads with lead sources

Each broker auto-tags inbound leads with its source value. For finer attribution (per Wattfox channel, per broker package, per campaign), use your workspace's lead-source taxonomy:

1. Open Settings > Lead generation > Lead sources and create lead sources for each broker channel or package you want to track.
2. Inbound leads can be mapped to a lead source via the broker's metadata (for example the Wattfox distribution channel ID, or an Aroundhome broker-side code); check the per-broker mapping with your account manager.
3. Filter your Requests inbox or your dashboard by lead source to see which broker and channel actually converts.

Disconnect or rotate credentials

If a broker contract ends, or you need to rotate API credentials:

1. Open the broker's row in Settings > Company settings > Integrations.
2. Click Disconnect.
3. To reconnect with new credentials, fill in the form again.

Note: Rotation is disconnect-then-reconnect via the Disconnect button, which briefly pauses the sync. Schedule rotations for off-hours if you're high-volume, and coordinate with your broker so they pause sending during the rotation window. To pause Bitrix without dropping credentials, set its sync lead scope to None instead. For other brokers, ask your broker to pause sending while you keep the connection in place.

Things to know

• Each broker stores its own lead ID on the request, so if the same broker re-sends the same lead, Reonic recognizes the duplicate and dedups it against the prior request.
• Cross-broker dedup is contact-based. If Wattfox and Aroundhome both sell you the same homeowner, you'll get two leads, because the broker IDs differ. Spot-check your fresh inbound by customer email if you suspect cross-broker overlap.
• Watch that leads keep arriving. You'll notice if leads stop coming in. If you suspect a broker has gone quiet, contact Reonic support with the broker name and the approximate time window.
• Cadence is broker-controlled. Some brokers deliver instantly (Bitrix); some deliver on their own schedule, a few times per day (Aroundhome, Wattfox, DAA, Eza, Interlead). Ask your account manager which brokers run on faster cadences if you need a tighter turnaround.
• The broker decides which fields it sends, and Reonic stores what it gets. If a broker sends incomplete contact info, talk to your broker contact about their export settings; some brokers gate richer payloads behind higher-tier packages.
• Broker leads add no per-lead cost in Reonic. Broker leads create Request rows within your plan. Inbound broker integrations carry no per-broker fee; the cost you bear is on the broker side (per-lead fees, package subscriptions). Confirm your plan's included integrations with your account manager.
• Disconnecting a broker stops only the inbound flow. Existing requests stay in your kanban and continue syncing to your outbound CRM (HubSpot, Pipedrive). The broker's own downstream reporting runs independently of Reonic.

Need help?

• Step-by-step questions about this flow → contact your Reonic account manager.
• Feature requests / something missing → drop a note to your account manager.
• Bug reports → include a screenshot and describe where in the app it happened in your support email.

Last updated on August 4, 2026