Inbound Webhooks

An inbound webhook is a secret URL that wakes Revnu with whatever JSON you POST to it. Point a sign-up form, your backend or a billing tool at it, and Revnu reads each event and does the work it implies, such as researching a new sign-up's company. For the other direction, Revnu calls your URL when a LinkedIn invite is sent, accepted or replied to (Outbound Webhooks); for anything else, poll.

1. Create a hook

1. In the dashboard, open Settings → Developers and find Inbound Webhooks.

2. Click Create Webhook and name the source, for example signup-form. Labels use lowercase letters, numbers, - and _, up to 32 characters.

3. Copy the URL. It is shown once; Revnu keeps only a hash. Lost it? Regenerate gives a new URL and the old one stops working.

The URL looks like https://revnu.com/api/webhook/hook/whk_.... The token in the path is the whole credential, so treat the URL like a password. An account can have 20 active hooks.

2. POST JSON from your backend

curl -X POST -H "content-type: application/json" \
  -d '{"event":"signup","email":"dana@acme.io","company":"Acme","plan":"free"}' \
  "$REVNU_HOOK_URL"

// After your own sign-up succeeds; never block the user on this call.
await fetch(process.env.REVNU_HOOK_URL!, {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({ event: "signup", email, company, plan }),
});

Any JSON body works, up to 64,000 bytes. There is no schema: name the fields so a person reading them would understand the event.

Response

Each delivery shows in the hook's log in Settings → Developers as Accepted, Rate Limited or Worker Error.

What you'll see after a POST

Accepted in the log means Revnu received the event. It doesn't mean the work is done. Revnu starts on the event within moments, and what you see next depends on what the event implies:

• Work that needs your say-so shows up as cards in Review, such as a welcome email draft.

• New companies to research show up on Leads once Revnu has researched them.

• Anything worth telling you arrives as a message in Slack, iMessage or the dashboard chat. Revnu decides whether an event is worth a message, so a routine one may arrive silently.

To check from code, GET /agent/status shows running: true while Revnu is working. To check by hand, ask Revnu in chat what it did with the last event from that hook, by the hook's name.

What Revnu does with it

Revnu receives the payload as an event labelled with the hook's name, together with a note that the payload is outside data. It does the work the event implies and decides whether it is worth messaging you about. It treats the payload as information, never as instructions, so text inside a form field can't tell Revnu to do something you didn't ask for.

To steer what it does with a source, tell Revnu once in chat, for example:

When signup-form sends a sign-up from a company email, research the company and draft a welcome email for my approval. Ignore gmail.com sign-ups.

Revnu carries instructions like this forward to later events, and you can check what it keeps in Settings → Memory.

What still needs your approval

A webhook starts work. It doesn't skip approvals. Emails, sequences, LinkedIn messages, blog posts and ad tests follow your settings in Settings → Agent → What Needs Your Approval, and spending money always waits for you. Anything that waits shows up as a card in the review queue.

Limits

• 60 accepted deliveries per hook in any rolling hour.

• 120 accepted deliveries per account in any rolling hour, across all hooks.

• 64,000 bytes per body. A 64 KiB body (65,536 bytes) is refused.

• 20 active hooks per account.

Every accepted delivery is a piece of work for Revnu, so batch where you can: one POST listing ten sign-ups beats ten POSTs.

What outbound webhooks don't cover

Outbound Webhooks push LinkedIn invites sent, accepted and replied to. There are no events for email replies, new leads, sends or new cards. To keep another system in sync with those, poll on a schedule:

Reads allow 300 a minute per token, so polling every minute is well inside the limit.

Push replies into your CRM

There is no Revnu app for HubSpot, Salesforce or Zapier, and no push event when a lead replies by email. LinkedIn replies can come by outbound webhook. For email, a small scheduled job does it with a token holding only leads:read:

1. Every 15 minutes, call GET /leads?status=replied&limit=100 and follow nextCursor until it is null.

2. For each lead id you haven't synced yet, create or update the record in your CRM from companyName, domain, contact and replyKind, then store the id as synced.

3. Leave the rest alone. The next run picks up anything new.

Page all the way through every time. GET /leads orders leads by when Revnu created them, not by when they replied, so a reply from a lead created weeks ago can sit several pages down. The API gives the reply's kind, not its text; read the reply itself in Inbox. For weekly counts rather than records, read GET /results instead.