Skip to content
English
  • There are no suggestions because the search field is empty.

How do I set up 12Build webhooks?

Learn how to set up webhooks to automatically receive updates to 12Build data and process them in external applications.

What will you find in this article?

  • Summary: How webhooks work within 12Build.

  • Prerequisites and target audience: What you need for the configuration.

  • The setup: How to create a new endpoint.

  • The Webhook message: Information about delivery and JSON structure.

  • Available objects: What data you can access.

  • Relational data: Managing your own data via the API.

  • Frequently Asked Questions (FAQ): Questions about limits and inactivity.

  • Troubleshooting: What to do if deliveries fail.


Summary

Webhooks make it possible to "push" changes in 12Build data directly to external applications. Instead of manually retrieving data, 12Build sends a notification to an endpoint you’ve set up as soon as a relevant change occurs.

Requirements and Target Audience

This feature is intended for administrators or developers who wish to integrate 12Build with other systems.

  • Relationships: Notifications are only sent for subcontractors with whom a relationship exists (marked with a green, gold, or black star).

  • Limit: The webhook feature works for up to 3,000 contacts.

9X_7INVpZ3TbH8pQUfjDeK1Bfjm6DpPzyXx_5iuotEst3oRTo48sWoji3BJ7OkjRYYmOHRypuVKldzPImNZ83kSl420xvdWi2OAYJ6-ZC5tS49GVic3zilQaxPXMHE-QRjl4uccR

Setup

You configure the webhooks within your organization’s general settings.

  1. Navigate to the Company Profile settings.

  2. Navigate to the Webhooks section.

  3. Create a new webhook and specify the desired endpoint (the URL of your external application).

  4. Select the specific objects and events for which you wish to receive a notification.

The Webhook Message

When a system change matches your settings, a JSON message is sent.

  • Delivery guarantee: If a delivery attempt fails (no HTTP 2xx response or a timeout), 12Build will attempt to resend the message up to 3 times.

  • Inactive: If a webhook has not had a single successful delivery for 3 days, it is automatically set to inactive.

  • Structure: The body contains JSON data with fields such as webhookId, action, object, timestamp, and both the current (current) and previous (previous) data of the object.

Available objects

Currently, you can set up webhooks for the following five objects:

  • Company

  • CompanyRelation

  • CompanyRelationData

  • Document

  • Message

Relational data

It is possible to add your own relational data to relationships for your exclusive use.

  • Management: There is currently no interface in 12Build to manage this data.

  • API: Use the API functions to manage relational data via:

    • getRelations

    • addRelationData

    • removeRelationData

    • updateRelationData


Frequently Asked Questions (FAQ)

Question: Why am I not receiving notifications from certain subcontractors? Answer: Webhooks only send data from companies marked as contacts (favorites with a star). Check whether the subcontractor in question has star status.

Question: What happens if my server is temporarily offline? Answer: 12Build attempts to send the message up to four times. Note that the webhook is automatically disabled after 3 days without successful delivery.

Troubleshooting

  • Symptom: The webhook is set to inactive.

    • Cause: No successful connection has been made to your endpoint in the past 3 days (no HTTP 200-series response).

    • Solution: Check the availability and logs of your endpoint and reactivate the webhook in the company profile settings.