VC Deal Flow Signal TRIGGER
New Engineering Signal
period + name + signalType. Optional filter by signal type.- Trigger
- Polling
- API key
- Webhook delivery
IMPLEMENTATION
Deploy this event source
Connect the user's VC Deal Flow Signal 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: "vc_deal_flow_signal-new-engineering-signal",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
vc_deal_flow_signal: { authProvisionId: "apn_xxxxxxx" },
signalTypeFilter: "Signal Type Filter",
timer: { "intervalSeconds": 900 },
},
webhookUrl: "https://example.com/webhooks/vc-deal-flow-signal",
})
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": "vc_deal_flow_signal-new-engineering-signal",
"webhook_url": "https://example.com/webhooks/vc-deal-flow-signal",
"configured_props": {
"vc_deal_flow_signal": { "authProvisionId": "apn_xxxxxxx" },
"signalTypeFilter": "Signal Type Filter",
"timer": { "intervalSeconds": 900 }
}
}'MCP servers expose VC Deal Flow Signal actions as on-demand tools.
New Engineering Signal 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 |
|---|---|---|
signalTypeFilter Signal Type Filter | string | Optional enum filter for engineering-signal type. Accepts one of the SIGNAL_TYPES, e.g. 'Deploy frequency spike', 'Infrastructure buildout'. Optional |
timer Timer | $.interface.timer | Required |
LIFECYCLE
Event delivery
01
Connect
Your user authorizes VC Deal Flow Signal 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
- vc_deal_flow_signal-new-engineering-signal
- Version
- 0.0.1
- App
- VC Deal Flow Signal
- Authentication
- API key
- Delivery
- Polling source
- Output
- Events emitted by VC Deal Flow Signal.
- Source
- View on GitHub ↗