# New or Modified Records in View — Airtable

> Emit new event for each new or modified record in a view

- Key: `airtable_oauth-new-or-modified-records-in-view`
- Type: Trigger (Polling)
- Version: 0.0.16
- App: Airtable (`airtable_oauth`) — https://pipedream.com/apps/airtable-oauth.md
- This page (HTML): https://pipedream.com/apps/airtable-oauth/triggers/new-or-modified-records-in-view
- Source: https://github.com/PipedreamHQ/pipedream/blob/master/components/airtable_oauth/sources/new-or-modified-records-in-view/new-or-modified-records-in-view.mjs

## Props

| Prop | Type | Required | Description |
|---|---|---|---|
| `timer` | `$.interface.timer` | Yes | Timer |
| `baseId` | `string` | Yes | The ID of the base to use, e.g. appXXXXXXXXXXXXXX. Use List Bases to look one up. |
| `filterByFormula` | `string` | No | Optionally provide a formula (see info on the documentation) used to filter records. The formula will be evaluated for each record, and if the result is not 0, false, "", NaN, [], or #Error! the record will be included in the response. For example, to only include records where Name isn't empty, use NOT({Name} = ''). |
| `tableId` | `string` | Yes | The table ID to watch for changes. |
| `viewId` | `string` | Yes | The view ID to watch for changes. |
| `returnFieldsByFieldId` | `boolean` | No | If set to true, the returned field objects will have the field ID as the key, instead of the field name. |

## Returns

Events emitted by Airtable.

## 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: "airtable_oauth-new-or-modified-records-in-view",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    airtable_oauth: { authProvisionId: "apn_xxxxxxx" },
    timer: { "intervalSeconds": 900 },
    baseId: "Base",
  },
  webhookUrl: "https://example.com/webhooks/airtable-oauth",
})

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": "airtable_oauth-new-or-modified-records-in-view",
    "webhook_url": "https://example.com/webhooks/airtable-oauth",
    "configured_props": {
      "airtable_oauth": { "authProvisionId": "apn_xxxxxxx" },
      "timer": { "intervalSeconds": 900 },
      "baseId": "Base"
    }
  }'
```

**MCP**

MCP servers expose Airtable actions as on-demand tools.

New or Modified Records in View 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/airtable-oauth.md · All apps: https://pipedream.com/apps