Orca Scan TRIGGER
New Row in Orca Scan Sheet
- Trigger
- Polling
- API key
- Webhook delivery
IMPLEMENTATION
Deploy this event source
Connect the user's Orca Scan account, configure the source, and choose the webhook where your backend receives events.
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: "orca_scan-new-row",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
orca_scan: { authProvisionId: "apn_xxxxxxx" },
timer: { "intervalSeconds": 900 },
sheetId: "Sheet ID",
},
webhookUrl: "https://example.com/webhooks/orca-scan",
})
console.log(deployed.id)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": "orca_scan-new-row",
"webhook_url": "https://example.com/webhooks/orca-scan",
"configured_props": {
"orca_scan": { "authProvisionId": "apn_xxxxxxx" },
"timer": { "intervalSeconds": 900 },
"sheetId": "Sheet ID"
}
}'MCP servers expose Orca Scan actions as on-demand tools.
New Row in Orca Scan Sheet 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.MCP exposes on-demand actions. Event sources are deployed through the Connect SDK or API because they continue listening after the initial request.
SCHEMA
Configuration
These inputs define which events the source watches. Dynamic options are loaded from the connected account.
| Property | Type | Description |
|---|---|---|
timer Timer | $.interface.timer | Required |
sheetId Sheet ID | string | The ID of the sheet where the row will be created or updated. Required Dynamic |
LIFECYCLE
Event delivery
01
Connect
Your user authorizes Orca Scan through Pipedream managed auth.
02
Deploy
Your backend deploys this source with that user's own configuration.
03
Webhook delivery
Every event is sent to the HTTP endpoint you choose when you deploy the source — after each poll.
OR
On-demand retrieval
No webhook required. Your app or agent can fetch recent events from the trigger events API.
REFERENCE
Trigger details
- Registry key
- orca_scan-new-row
- Version
- 0.0.1
- App
- Orca Scan
- Authentication
- API key
- Delivery
- Polling source
- Output
- Events emitted by Orca Scan.
- Source
- View on GitHub ↗