# Entity Updated — Fibery

> Emit new event for every updated entity of a certain type. See the docs here

- Key: `fibery-entity-updated`
- Type: Trigger (Instant)
- Version: 0.0.1
- App: Fibery (`fibery`) — https://pipedream.com/apps/fibery.md
- This page (HTML): https://pipedream.com/apps/fibery/triggers/entity-updated
- Source: https://github.com/PipedreamHQ/pipedream/blob/master/components/fibery/sources/entity-updated/entity-updated.mjs

## Description

Emit new event for every updated entity of a certain type. [See the docs here](https://api.fibery.io/#webhooks)

## Props

| Prop | Type | Required | Description |
|---|---|---|---|
| `type` | `string` | Yes | A custom type in your Fibery account Options are loaded from the connected account. |

## Returns

Events emitted by Fibery.

## Run it

**TypeScript**

```ts
import { PipedreamClient } from "@pipedream/sdk"

const pd = new PipedreamClient({
  projectId: process.env.PIPEDREAM_PROJECT_ID!,
  clientId: process.env.PIPEDREAM_CLIENT_ID!,
  clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
  projectEnvironment: "production",
})

const deployed = await pd.triggers.deploy({
  id: "fibery-entity-updated",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    fibery: { authProvisionId: "apn_xxxxxxx" },
    type: "Type",
  },
  webhookUrl: "https://example.com/webhooks/fibery",
})

console.log(deployed.id)
```

**cURL**

```bash
curl -X POST https://api.pipedream.com/v1/connect/{project_id}/triggers/deploy \
  -H "Content-Type: application/json" \
  -H "X-PD-Environment: production" \
  -H "Authorization: Bearer {access_token}" \
  -d '{
    "external_user_id": "{external_user_id}",
    "id": "fibery-entity-updated",
    "webhook_url": "https://example.com/webhooks/fibery",
    "configured_props": {
      "fibery": { "authProvisionId": "apn_xxxxxxx" },
      "type": "Type"
    }
  }'
```

**MCP**

MCP servers expose Fibery actions as on-demand tools.

Entity Updated is an event source, so your application deploys it with the Connect SDK or API and then either receives each event at a webhook URL or retrieves events on demand with the trigger events API.

## Event delivery

Every event is sent to the HTTP endpoint you choose when you deploy the source. Or: no webhook required — your app or agent can fetch recent events from the [trigger events API](https://pipedream.com/docs/connect/api-reference/list-trigger-events.md) instead.

---

- App: https://pipedream.com/apps/fibery.md · All apps: https://pipedream.com/apps