Webhooks

Reo.Dev’s Webhooks feature enables real-time data transmission from Reo.Dev to external systems. This unlocks powerful automation workflows, allowing sales and marketing teams to:

• Get instant Slack alerts when high-intent accounts or developers enter a segment.

• Automatically add new leads to dynamic email sequences tools or LinkedIn outreach campaigns.

• Sync new accounts with CRM systems like Salesforce, HubSpot, or Pipedrive.

• Enrich advertising audiences by syncing accounts to LinkedIn Ads or other ad platforms.

• Contextualize outreach using activity-based triggers, such as a developer initiating a package installation.

Note: This feature is only available for customers with Data Out API Add-on (Product API, Zapier, Webhooks, etc) in their plans.

To enable Webhooks, contact your Customer Success Representative via Slack or email us at [e-mail]

---

Navigating to Webhooks

1. Go to: Settings → Integrations.

2. Find the Webhooks tile and click "Configure".

You will see the Webhooks dashboard listing all created webhooks, their status, and last updated activity time.

---

Creating a Webhook

Only users with Admin role permissions in Reo.Dev can create and map Webhooks.

To create a webhook, follow these steps:

1. Click "Create Webhook" on the Webhooks dashboard.

2. Fill in the required details:

   • Webhook Name → Give a descriptive name.

   • Payload Type → Choose from Accounts, Developers, or Activities.

   • Destination URL → Enter the external system’s API endpoint (e.g., a Zapier webhook URL).

3. Click "Submit" to create the Webhook.

---

Webhook Triggers & Events

Reo.Dev currently supports four types of Webhook triggers:

Event	Trigger Type	Frequency
New Account added to an account segment	Account Segment	Once per day
New Developer added to a developer segment	Developer Segment	Once per day
New activity in an account segment	Account Activity	Instant
New activity in a developer segment	Developer Activity	Instant

• Account & Developer Segments → Data refreshes every 24 hours, so new accounts/developers are added once a day.

• Activity Webhooks → Trigger instantly whenever an activity occurs.

Best Practice:

Always create a Webhook first before mapping it to a segment. Use clear, descriptive names to easily recognize Webhooks when mapping them.

---

Testing Webhooks & Sample Payloads

Before using a Webhook, test if data is reaching the destination URL:

• Open the Webhooks dashboard.

• Click the Test Webhook icon next to a created Webhook.

• The system will send a sample payload to the configured destination URL.

• If successful, you will see a confirmation message.

• If the URL is incorrect or unreachable, an error message appears:

To fix it: Check if the URL is correct and the endpoint is configured to accept data.

Note:

• The test only verifies if the sample payload is successfully received at the destination URL.

• It does NOT test webhook behavior after mapping it to a segment.

• Even if a Webhook is mapped to a segment, the Test Webhook function will not send actual segment data but will always use Reo.Dev’s predefined sample payload for testing.

---

Sample Payloads

Account Payload Example

{
    "org_id": "03e19e88-5b3e-4f58-b21b-aa7d737d8d19",
    "account_name": "Reo.Dev",
    "account_domain": "reo.dev",
    "country": "United States",
    "first_activity_date": "2024-12-31 19:00:01",
    "last_activity_date": "2025-02-15 21:00:01",
    "customer_fit": "STRONG",
    "developer_activity": "HIGH",
    "active_developers_count": 10,
    "segment_id": "e7303e53-6387-4726-b6ff-93b5910c6ad3",
    "segment_name": "Reo.Dev Org Test Segment"
}

---

Developer Payload Example

{
    "developer_id": "e2eb4d5c-a1f8-40ff-a50a-dc088ec99600",
    "developer_name": "John Doe",
    "country": "United States",
    "developer_linkedin": "https://www.linkedin.com/company/john-doe",
    "developer_github": "https://github.com/github-john-doe",
    "developer_business_email": "[e-mail]",
    "first_activity_date": "2024-12-31 19:00:01",
    "last_activity_date": "2025-02-15 21:00:01",
    "segment_id": "e7303e53-6387-4726-b6ff-93b5910c6ad3",
    "segment_name": "Reo.Dev Developer Segment",
    "account": {
        "org_id": "03e19e88-5b3e-4f58-b21b-aa7d737d8d19",
        "account_name": "Reo.Dev",
        "account_domain": "reo.dev",
        "country": "United States",
        "first_activity_date": "2024-12-31 19:00:01",
        "last_activity_date": "2025-02-15 21:00:01",
        "customer_fit": "STRONG",
        "developer_activity": "HIGH",
        "active_developers_count": 10
    }
}

---

Activity Payload Example

{
    "activity_id": "1671f26c-92ac-48d8-9fc8-1b58c28c6ac8",
    "activity_type": "PAGE_VISIT",
    "source_type": "DOCUMENT",
    "activity_date": "2024-12-31 19:00:01",
    "segment_id": "e7303e53-6387-4726-b6ff-93b5910c6ad3",
    "segment_name": "Reo.Dev Developer Activites Segment",
    "segment_type": "DEVELOPER",
    "developer": {
        "developer_id": "e2eb4d5c-a1f8-40ff-a50a-dc088ec99600",
        "developer_name": "John Doe",
        "country": "United States",
        "developer_linkedin": "https://www.linkedin.com/company/john-doe",
        "developer_github": "https://github.com/github-john-doe",
        "developer_business_email": "[e-mail]",
        "first_activity_date": "2024-12-31 19:00:01",
        "last_activity_date": "2025-02-24 19:00:01",
        "account": {
            "org_id": "03e19e88-5b3e-4f58-b21b-aa7d737d8d19",
            "account_name": "Reo.Dev",
            "account_domain": "reo.dev",
            "country": "United States",
            "first_activity_date": "2024-12-31 19:00:01",
            "last_activity_date": "2025-02-24 19:00:01",
            "customer_fit": "STRONG",
            "developer_activity": "HIGH",
            "active_developers_count": 10
        }
    }
}

---

Editing, Pausing, & Deleting Webhooks

• Edit Webhook: You can modify the name and destination URL. If already mapped to a segment, the new URL will start receiving data automatically.

• Pause Webhook: Temporarily stops data flow to the endpoint. Can be resumed anytime.

• Delete Webhook: Removes it permanently, along with all stored webhook data.

---

Mapping Webhooks to Segments

Note: As of today, Webhooks currently can only be mapped to Account & Developer Segments (not Buyer Segments).

How to Map a Webhook

• Open the Segments panel.

• Click "Configure Webhook" for an Account or Developer segment.

• In the mapping popup modal:

  • For Account Segments, only Account and Activity payload type Webhooks will be listed.

  • For Developer Segments, only Developer and Activity payload type Webhooks will be listed.

  • Account payload Webhooks cannot be mapped to Developer Segments.

• Select the Webhook(s) you want to map.

• Save the selection.

---

First-Time Sync & Incremental Updates

• When mapping a Webhook for the first time, all existing data in the segment is sent.

• After that, only new accounts/developers added to the segment will be sent.

• Activity Webhooks do NOT perform first-time syncs (to prevent system overload).

---

Error Handling & Audit Logs

• Webhook failures → If a webhook fails, one retry is attempted.

• No audit logs (yet) → Currently, webhook logs/errors are not visible in the UI.

• Planned improvements → Audit logs and better error tracking will be introduced soon.

• Need help? Contact support via Slack or email [e-mail]

---

Webhook Event Types & Data Fields

Reo.Dev Webhooks capture and send various event types related to developer and account activities across multiple sources. Below is a structured list of the unique activity_type and source_type values currently supported in Webhooks.

Supported Activity & Source Types

GitHub (source_type: "GITHUB")

• "activity_type": "FORK"

• "activity_type": "STAR"

• "activity_type": "COMMENT"

• "activity_type": "ISSUE_CREATION"

• "activity_type": "PULL_REQUEST"

• "activity_type": "WATCH"

Documentation (source_type: "DOCUMENT")

• "activity_type": "PAGE_VISIT"

• "activity_type": "COPY_TEXT"

• "activity_type": "COPY_PACKAGE_MANAGER"

• "activity_type": "COPY_COMMAND"

• "activity_type": "FORM_CAPTURE"

Website (source_type: "WEBSITE")

• "activity_type": "PAGE_VISIT"

• "activity_type": "COPY_TEXT"

• "activity_type": "COPY_PACKAGE_MANAGER"

• "activity_type": "COPY_COMMAND"

• "activity_type": "FORM_CAPTURE"

Product (source_type: "PRODUCT_JS")

• "activity_type": "Identity"

• "activity_type": "PAGE_VISIT"

• "activity_type": "COPY_TEXT"

• "activity_type": "COPY_PACKAGE_MANAGER"

• "activity_type": "COPY_COMMAND"

Code Interactions (source_type: "CODE_INTERACTIONS")

• "activity_type": "INTERACTION_COPY_COMMAND"

• "activity_type": "INTERACTION_COPY_PACKAGE_MANAGER"

Slack (source_type: "SLACK")

• "activity_type": "SLACK_MESSAGE"

• "activity_type": "SLACK_REPLY"

• "activity_type": "SLACK_REACTION"

• "activity_type": "SLACK_JOINED"

LinkedIn (source_type: "LINKEDIN")

• "activity_type": "LINKEDIN_MESSAGE"

• "activity_type": "LINKEDIN_REPLY"

• "activity_type": "LINKEDIN_REACTION"

---

Filtering & Processing: By using activity_type and source_type, your system can categorize and process webhook data efficiently.

These values determine what kind of developer actions are tracked and the origin of those actions, enabling teams to automate workflows based on real-time developer activity.

Data Format Example

Webhook payloads follow a structured JSON format like this:

{
    "activity_type": "PAGE_VISIT",
    "source_type": "DOCUMENT"
}

---

FAQs

Can I map a Webhook to multiple segments?

Yes, a single webhook can be linked to multiple segments.

How frequently is segment data updated?

New data in for Segments is refreshed every 24 hours. Activity Webhooks trigger instantly.

What happens if I change the Webhook’s destination URL?

All mapped segments will start sending data to the new URL automatically.

How do I debug Webhook failures?

Check if the destination URL is correct and the system is configured to accept webhook data. For any other errors or failures, please reach out to us on Slack or via email at [e-mail]

---

Need Further Assistance?

If you encounter any issues, reach out to our team via:

📧 Email → [e-mail] 💬 Slack → Contact your CSM