Skip to main content
Make a table that an app adds rows to as things happen, such as a website visit, a form response, or a new lead. Some apps get the URL from Oneprofile through a connection. For the rest, you paste it in.
The Get data from a webhook panel listing the apps that can send rows, with RB2B visitors selected and a Table name field below the list.

The Get data from a webhook panel, with RB2B visitors picked.

Make a webhook table

1

Open the drawer

On Tables, choose the Get data from a webhook card under Ways to start. New lists the same item.
2

Pick what sends the rows

Under What sends the rows, choose a source, such as RB2B visitors or Any app that sends JSON. Change the Table name if you like.
3

Create the table

Click Create table. The table opens with its Source panel, which shows the webhook URL.
A source that sends through a connection also asks for its Connection.

Pick how the app gets the URL

  • Typeform, Pipedrive, Attio, Calendly, and Mailchimp send through a connection. Oneprofile registers the URL with the app, so there is nothing to paste.
  • RB2B, Salesforce outbound messages, and any app that sends JSON need the URL pasted in. The Source panel lists the steps.
  • Facebook Lead Ads takes both, plus two secrets under Secrets.

Send RB2B visitors

1

Copy the URL

In the table’s Source panel, click Copy beside the webhook URL.
2

Paste it into RB2B

In RB2B, open Integrations, then Webhook. Paste the URL and save.
3

Send a test

Press Send a Test Event in RB2B. The panel shows Test received, and the test adds no row.
Each visitor RB2B identifies gets a row, with a column for each fact RB2B sends, such as name, company, and work email.

Send from any app

Add a webhook that sends JSON in your app, and paste the URL as its address. Each delivery is kept whole in the table’s record column. Open a row’s record cell and choose Add as a column to give any field its own column. In the drawer, fill in Match rows on with the field that tells rows apart, such as email. A later delivery with the same value updates that row.

Fix failed deliveries

Deliveries counts what the URL received in the last 24 hours and in all. Failed deliveries lists each one that did not fit, newest first, with the fields that went wrong. Fix the cause, then click Retry to read it again and add what fits.

Replace or revoke the URL

Click Replace URL when a URL leaked. Choose Keep the old URL working for 7 days while you update the app, or Stop the old URL now. Revoke URL stops the rows for good, and every row stays. Make a new URL starts them again later, with the same app and match field.

Good to know

The Source panel lists these steps beside the URL.
  1. In Salesforce, open Setup, search for Outbound Messages, and click New Outbound Message.
  2. Pick the table’s object, paste the URL into Endpoint URL, and leave Send Session ID unticked.
  3. Add Id, SystemModstamp, and every field the table shows, then save.
  4. In Flow Builder, make a record-triggered flow on the same object that runs when a record is created or updated. Add the message as its action and activate the flow.
Salesforce sends nothing when a record is deleted, so a deleted record stays in the table.
The Source panel lists these steps beside the URL.
  1. Under Secrets, paste your Meta app’s App secret as the Signing secret, and a Verify token you make up. Click Save beside each.
  2. In Meta for Developers, open your app’s Webhooks settings, pick Page, and click Subscribe to this object.
  3. Paste the URL into Callback URL and your verify token into Verify token, then click Verify and save.
  4. In the list of Page fields, subscribe to leadgen.
Until the signing secret is saved, rows from Meta are refused. Until the verify token is saved, Meta can’t check the URL.
Click Replace, paste the new one, and click Save. Choose Keep the old secret working for 36 hours while you update the app, or Stop the old secret now.Clear removes a secret. The app’s rows are refused, or its check of the URL fails, until a new one is saved. The panel only ever shows a secret’s last characters.
The connection names what is watched, such as a Typeform connection’s form or a Mailchimp connection’s audience. When the workspace has one connection to the app, it is picked for you. With no connection to the app yet, the drawer says to connect it in Settings, under Connections, first. Until a connection is picked, Create table says “Pick a connection first”.
For a source that sends through a connection, the panel shows one notice until the app sends:
  • “Registering the webhook with Typeform…” while it is being set up, or set up again after the app lost it.
  • “refused to register the webhook” means the connection lacks permission to manage webhooks. Reconnect the app with that permission, then replace the URL.
  • “didn’t answer”, “turned this webhook off”, or “didn’t give a signing secret” means rows stopped. Click Replace URL to register it again.
  • “missing a setting the webhook needs, such as a Page ID” means the connection is not filled in. Fill it in on the connection, then replace the URL.
  • “connection this webhook was registered through was deleted” means rows stopped. Revoke the URL, connect the app again, then make a new URL.
No notice means the webhook works.
The panel says why it paused and offers Resume. Fix what it names first, then click Resume to take rows again.
The drawer says so under the source when it matters. RB2B sends webhooks on its Pro plan, and Typeform on every plan, the free one included. Mailchimp sends on its Standard and Premium plans. Salesforce outbound messages need Enterprise, Unlimited, Performance, or Developer edition.
Not to a new one. Import from the tool, then turn on live changes, and its changes reach the table as they happen. See Get live changes from a tool.
The URL works like a password: anyone who has it can add rows to the table. The AI Assistant can make the table and change its URL, but it never sees the URL. It links you to the Source panel, where you copy it.
Yes. RB2B sends to one webhook per account, so pasting this URL replaces any webhook already saved there.
Turn on “Send repeat visitor data” in RB2B to update the visitor’s row on each later visit. Only when they were seen, the page, and the referrer change. A column that costs credits doesn’t run again for a repeat visit.
Yes. Turn on “Sync company-only profiles” in RB2B. Those visits arrive as company rows, matched on the website domain.
Every delivery adds a new row, even when it describes a row already in the table. The other sources tell their records apart themselves, so only Any app that sends JSON asks for this field.
Couldn’t read means nothing in the delivery fit. Partly added means some rows fit and were added. Too large means the delivery was over the size the app may send. Refused means it did not prove it came from the app, such as a signature that doesn’t match the saved secret.
The list keeps each failed delivery for 30 days, and Show more reads older ones. Retry works for 14 days after a delivery that did not fit. A delivery that was too large or refused can’t be retried.
“Nothing has arrived for 2 days” means the app may no longer have the URL saved. “Over 200 rows an hour arrived” means someone may have the URL who should not. Replace the URL if that wasn’t your app.
Deleting the table revokes its URL, so the app can no longer send to it. Restoring the table from Trash does not turn the URL back on. Use Make a new URL and paste it into the app again.

Next steps

Create a table

Every other way to start a table.

Get live changes from a tool

Keep an imported table current as the tool changes.

Enrichment columns

Add work emails, phone numbers, and company facts to each row.

AI Assistant

Ask the AI Assistant to make the table or check its deliveries.