> For the complete documentation index, see [llms.txt](https://agpt.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agpt.co/docs/integrations/block-integrations/webhook.md).

# Slant3D Webhook

Blocks for receiving webhook notifications about Slant3D order status updates.

## Slant3D Order Webhook

### What it is

This block triggers on Slant3D order status updates and outputs the event details, including tracking information when orders are shipped.

### How it works

This block subscribes to order events on a Slant3D platform. New v2 subscriptions require `platform_id="your-platform-id"`; only retained v1 subscriptions may omit it. Registration is serialized per platform to prevent competing callbacks. Each platform has one webhook URL, so an existing callback belonging to another application requires a dedicated platform. V2 deliveries must include `X-Webhook-Signature-256: sha256=<digest>` and a fresh millisecond `X-Webhook-Timestamp`; invalid signatures, platform mismatches, and invalid event types are rejected.

The block outputs order details and available tracking information. Missing carrier codes become empty strings, and dummy deliveries do not trigger workflows. Retained v1 callbacks have no signature scheme and rely on their unguessable callback URL as a bearer credential: keep that URL private. Reconnect with a v2 key and platform ID to migrate to signed delivery.

### Inputs

| Input        | Description                                                                                                                     | Type   | Required |
| ------------ | ------------------------------------------------------------------------------------------------------------------------------- | ------ | -------- |
| platform\_id | Required for new v2 subscriptions; retained v1 subscriptions may omit this platform ID. Use a platform without another webhook. | str    | No       |
| events       | Order status events to subscribe to                                                                                             | Events | No       |

### Outputs

| Output           | Description                                            | Type            |
| ---------------- | ------------------------------------------------------ | --------------- |
| error            | Error message if payload processing failed             | str             |
| payload          | The complete webhook payload received from Slant3D     | Dict\[str, Any] |
| order\_id        | The ID of the affected order                           | str             |
| status           | The new status of the order                            | str             |
| tracking\_number | Shipment tracking number, empty before shipment        | str             |
| carrier\_code    | Carrier code when supplied by Slant3D, otherwise empty | str             |

### Possible use case

**Customer Notifications**: Automatically notify customers via email or SMS when their 3D print order ships.

**Order Tracking**: Update your internal systems with shipping information when orders are fulfilled.

**Inventory Management**: Trigger restocking workflows when orders are completed.

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://agpt.co/docs/integrations/block-integrations/webhook.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.