Snowflake TRIGGER
New Query Results
- Trigger
- Polling
- API key
- Webhook delivery
IMPLEMENTATION
Deploy this event source
Connect the user's Snowflake 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: "snowflake-query-results",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
snowflake: { authProvisionId: "apn_xxxxxxx" },
timer: { "intervalSeconds": 900 },
sqlQuery: "SQL Query",
},
webhookUrl: "https://example.com/webhooks/snowflake",
})
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": "snowflake-query-results",
"webhook_url": "https://example.com/webhooks/snowflake",
"configured_props": {
"snowflake": { "authProvisionId": "apn_xxxxxxx" },
"timer": { "intervalSeconds": 900 },
"sqlQuery": "SQL Query"
}
}'MCP servers expose Snowflake actions as on-demand tools.
New Query Results 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 | Watch for changes on this schedule Required |
sqlQuery SQL Query | string | Run this query on a schedule, triggering the workflow for each row of results Required |
dedupeKey Primary key | string | The column in your query to use for de-duplication. Duplicate rows won't trigger your workflow Optional |
emitIndividualEvents Emit individual events | boolean | Defaults to true, triggering workflows on each record in the result set. Set to false to emit records in batch (advanced) Optional |
LIFECYCLE
Event delivery
01
Connect
Your user authorizes Snowflake 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
- snowflake-query-results
- Version
- 0.2.5
- App
- Snowflake
- Authentication
- API key
- Delivery
- Polling source
- Output
- Events emitted by Snowflake.
- Source
- View on GitHub ↗