RB2B

RB2B + Konnectify

RB2B Integration with Konnectify

Enrich visitor and identity signals (IPs, emails, and LinkedIn profiles) into business profiles and device identifiers, then route the results into downstream data workflows with Konnectify.

Credits Identity Enrichment 0 Triggers 19 Actions

ON THIS PAGE

→ What is RB2B? → API & Authentication → How to connect → Triggers (0) → Actions (19) → Popular automations → FAQ

What is RB2B?

RB2B helps identify website visitors and enrich identity signals by converting inputs like IP addresses, emails, and LinkedIn slugs into actionable business profiles and identifiers (for example, hashed emails and device IDs).

Connecting RB2B to Konnectify lets you standardize enrichment in your workflows—so sales ops, marketing ops, and data pipelines can automatically resolve identities, look up LinkedIn profiles, and track credit usage without manual steps.

New to RB2B?

Create an account and generate an API key to start enriching identities and visitor signals.

RB2B

Visit RB2B →

If this URL differs for your RB2B environment, use your organization’s official RB2B link.

New to Konnectify?

Build workflows that enrich, transform, and route RB2B signals into your CRM, warehouse, and messaging tools.

Konnectify

Create Konnectify account →

You can connect multiple RB2B accounts/workspaces later if needed.

What you can automate

• Track RB2B credit usage to avoid workflow interruptions

• Resolve an IP address to likely company domains with confidence

• Convert IPs and emails into hashed email identifiers (HEM) for matching

• Map emails/HEMs/IPs to device IDs (MAIDs) for audience enrichment

• Find LinkedIn profile URLs or slugs from emails and hashed emails

• Enrich LinkedIn/email/HEM into complete business profiles

API & Authentication

Authentication method: API Key

This RB2B connector uses API Key authentication. You’ll paste your RB2B API key into Konnectify when creating the connection. Keep the key secure and rotate it if you suspect it was exposed.

What the RB2B API is used for in Konnectify

Credit usage visibility (credit checks)
Identity resolution from IPs, emails, and hashed emails (HEM)
LinkedIn discovery (profile URL, slug search)
Business profile enrichment from email/HEM/LinkedIn
Device identity enrichment (MAIDs) from IP/email/HEM

Important: plan limits & rate limits

RB2B endpoints may be subject to credit consumption, plan-based access, and request rate limits. If your workflow runs at high volume, add guards (filters, caching, and retries with backoff) and monitor your RB2B credits.

API docs: Refer to RB2B’s official documentation (use the API/Docs section in your RB2B account or help center).

How to connect RB2B to Konnectify

Prerequisites

An RB2B account with an active plan and available credits
Your RB2B API Key
A Konnectify workspace where you can create/edit workflows

Add RB2B to a Workflow

Open Konnectify and create a new workflow (or edit an existing one).
Click Add step and search for RB2B.

Authorize via API Key authentication

Select Add new connection.
Paste your RB2B API Key into the API Key field.
Save the connection.

Configure the Trigger or Action

Choose the RB2B action you want to run (for example, enriching an email to a business profile).
Map input fields from previous steps (IP, email, HEM, LinkedIn URL/slug, name, company domain).
Decide how you’ll handle empty results (continue, branch, or stop).

Tip: Many RB2B enrichment calls can return no match depending on the input quality. Add a Konnectify Filter/Branch step after the RB2B action to handle null/empty fields and avoid writing partial data downstream.

Test the Workflow

Run a test with known-good inputs (a real company IP, a verified email, or a LinkedIn profile URL).
Confirm the output fields match your expectations before sending data to your CRM/warehouse.

Activate the Workflow

Turn the workflow On.
Monitor early runs, credit usage, and downstream write volume.

Triggers 0

This connector currently has no triggers. Use RB2B actions after a trigger from another app (for example, a new lead, form submission, or website event) to enrich and route data.

Actions 19

Use RB2B actions to enrich identities, resolve companies, find LinkedIn profiles, and map signals to hashed emails or device IDs.

Credits 1 actions

Credit Check

Retrieve your remaining RB2B credits to track usage and avoid interruptions.

IPs 4 actions

Resolve IP to Hashed Emails

Convert an IP address into hashed email identifiers to enrich visitor data and support identity resolution.

Resolve IP to Device IDs

Convert an IP address into Mobile Advertising IDs (MAIDs) to identify devices and enrich audience data.

Resolve IP to Company

Convert an IP address into likely company domains with match confidence to identify visiting organizations and enrich lead data.

Find LinkedIn Profile from Name and Company

Search and retrieve the most relevant LinkedIn profile using a person's name and company domain to support prospect discovery and enrichment workflows.

Emails 5 actions

Resolve Business Email to Personal HEM

Convert a business email address into hashed personal email identifiers to enrich user profiles and improve identity resolution.

Find LinkedIn Profile from Email

Retrieve the most relevant LinkedIn profile URL for a given email address to enrich user data and support prospect research.

Enrich Email to Business Profile

Retrieve a complete business profile from an email address, including name, company, role, LinkedIn, and additional enrichment data.

Find LinkedIn Slug from Email

Retrieve the LinkedIn profile slug for a given email address to support profile matching and enrichment workflows.

Resolve Email to Device IDs

Convert an email address into Mobile Advertising IDs (MAIDs) to identify associated devices and enrich audience data.

Hashed Emails (HEM) 4 actions

Find LinkedIn Profile from HEM

Retrieve the most relevant LinkedIn profile URL using an MD5 hashed email (HEM) to support identity resolution and enrichment workflows.

Enrich HEM to Business Profile

Retrieve a complete business profile using an MD5 hashed email (HEM), including name, company, role, LinkedIn, and additional enrichment data.

Find LinkedIn Slug from HEM

Retrieve the LinkedIn profile slug using an MD5 hashed email (HEM) to support profile matching and enrichment workflows.

Resolve HEM to Device IDs

Convert an MD5 hashed email (HEM) into Mobile Advertising IDs (MAIDs) to identify associated devices and enrich audience data.

LinkedIn Profiles 5 actions

Find Personal Email from LinkedIn

Retrieve the most relevant personal email address from a LinkedIn profile to support lead enrichment and outreach workflows.

Find Hashed Emails from LinkedIn

Retrieve hashed email identifiers (MD5 and SHA-256) from a LinkedIn profile to support identity resolution and enrichment workflows.

Find Mobile Number from LinkedIn

Retrieve the mobile phone number associated with a LinkedIn profile to support lead enrichment and direct outreach workflows.

Find Personal Emails from LinkedIn

Retrieve personal email addresses associated with a LinkedIn profile to support lead enrichment and outreach workflows.

Enrich LinkedIn to Business Profile

Retrieve a complete business profile from a LinkedIn profile, including name, role, company details, emails, and enrichment data.

Popular automations

Enrich inbound leads from email into a complete business profile

When a lead arrives from a form/CRM trigger, enrich the email to a full business profile (name, role, company, LinkedIn) before writing downstream.

Trigger from another app (e.g., New Lead) → Enrich Email to Business Profile

Resolve website visitor IP to company, then route to sales/analytics

Take an IP from a website event source and resolve the likely company domain(s) with confidence for account-based analytics or routing.

Trigger from another app (e.g., Web Event) → Resolve IP to Company

Find a LinkedIn profile from an email, then enrich to a business profile

If you only have an email address, discover the best matching LinkedIn profile and then enrich it for richer person/company attributes.

Trigger from another app (e.g., New Contact) → Find LinkedIn Profile from Email → Enrich LinkedIn to Business Profile

Monitor enrichment spend: credit check before high-volume runs

Before running large batches, check remaining credits and branch the workflow if credits are low to prevent failures.

Trigger from another app (e.g., Scheduled Run) → Credit Check

FAQ

How does authentication work for RB2B in Konnectify?

RB2B uses API Key authentication. Create or copy an API key from your RB2B account and paste it into the Konnectify RB2B connection. If a key is rotated or revoked, update the connection in Konnectify.

Which RB2B plans are supported?

Any RB2B plan that provides API access and sufficient credits should work. Availability of specific enrichment endpoints can vary by plan/contract—if an action returns an authorization or entitlement error, confirm your RB2B plan includes that capability.

How do triggers work for this integration—webhooks or polling?

The RB2B connector currently provides actions only (no native RB2B triggers). Start your workflow with a trigger from another app (CRM, forms, web events, schedules), then use RB2B actions to enrich the record.

How can I prevent duplicates when enriching data?

RB2B actions return enrichment results but do not “upsert” into your destination by themselves. To prevent duplicates, use Konnectify to:

Deduplicate by a stable key (email, LinkedIn URL/slug, or internal contact ID).
Search your destination first, then update/create accordingly.
Use branching when RB2B returns no match.

What happens if RB2B rate-limits my workflow?

If RB2B responds with rate-limit or transient errors, reduce concurrency, add retry with backoff, and consider batching upstream. Also monitor credits—some endpoints may fail when credits are depleted even if requests are valid.

Can I connect multiple RB2B accounts?

Yes. Create multiple RB2B connections in Konnectify—each with its own API key—and select the appropriate connection per workflow (or per step) based on environment, region, or business unit.

What is a HEM, and how should I format it?

HEM typically refers to a hashed email (in this connector, an MD5 hashed email). Hashing is usually performed on a normalized email string (trimmed, lowercased). If you already store HEMs, ensure they match RB2B’s expected hashing method; otherwise, use email-based actions (like “Enrich Email to Business Profile”) and only switch to HEM actions when needed for privacy-preserving matching.

Ready to automate your RB2B workflows?

Connect RB2B to Konnectify to enrich identities and route signals into the tools your team already uses.

Get started free →