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 — User-ID/API-Key pair plus your Bitrix24 domain

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

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, so 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.

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.

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 Eza

Eza ("Einfach zum Angebot") is a German PV / heat-pump comparison portal.

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 sync 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 (both directions)

Bitrix works in both directions at once: Reonic sends each new request to Bitrix, and a Bitrix automation can send records to Reonic. You set up both on the same Bitrix row.

1. Open Settings > Company settings > Integrations and find the Bitrix row in the CRM / deal sync section.
2. Enter your Bitrix24 Domain (for example mycompany.bitrix24.de) and your Bitrix User-ID/API-Key pair, in the form <userId>/<apiKey>. You create the pair in Bitrix24.
3. Click Save API key. When the credentials check out, the status changes to Connected.
4. Choose the Sync mode requests & offers:
   • Deal (the default): each new Reonic request creates a Bitrix Deal. Most Bitrix24 setups use this.
   • Lead: each new Reonic request creates a Bitrix Lead. Choose this only if your Bitrix24 uses Leads.
   • Without: sync to Bitrix pauses, and your credentials stay in place.

The mode is saved as soon as you pick it.

1. To receive records from Bitrix, go to Endpoint for offer creation below the sync mode, click the sync icon to generate the endpoint URL, and copy it.
2. In Bitrix24, add an outgoing-webhook step to the automation that should create the request in Reonic, and paste the URL as its target.

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, and your welcome-email template fires if configured.
4. You work the lead in Reonic. From your kanban: qualify, create an offer, sign, and hand off to installation, all the standard Request lifecycle.

Tag broker leads with lead sources

Each broker auto-tags inbound leads with its own source label. For finer attribution (per 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 using the broker's metadata (for example a distribution channel or a package code). Contact the support chat for the per-broker mapping.
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.

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.
• Cadence is broker-controlled. Some brokers deliver instantly; some deliver on their own schedule, a few times per day.
• 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 create Request rows in Reonic like any other request. For pricing, billing, or license questions, contact the support chat.
• New broker leads appear in your Requests kanban as they arrive.
• Disconnecting a broker stops only the inbound flow. Existing requests stay in your kanban and keep syncing to your outbound CRM (HubSpot, Pipedrive). The broker's own reporting runs independently of Reonic, so closing or losing a lead in your kanban doesn't update the broker's side.
• Bitrix runs both directions at once. The sync mode decides which Bitrix record Reonic creates (Deal or Lead). The inbound endpoint is set up separately and works alongside it.

Last updated on October 2, 2026