Neo4j AuraDB TRIGGER
New Node Created
- Trigger
- Polling
- API key
- Webhook delivery
IMPLEMENTATION
Deploy this event source
Connect the user's Neo4j AuraDB 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: "neo4j_auradb-new-node",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
neo4j_auradb: { authProvisionId: "apn_xxxxxxx" },
timer: { "intervalSeconds": 900 },
orderBy: "Order By",
},
webhookUrl: "https://example.com/webhooks/neo4j-auradb",
})
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": "neo4j_auradb-new-node",
"webhook_url": "https://example.com/webhooks/neo4j-auradb",
"configured_props": {
"neo4j_auradb": { "authProvisionId": "apn_xxxxxxx" },
"timer": { "intervalSeconds": 900 },
"orderBy": "Order By"
}
}'MCP servers expose Neo4j AuraDB actions as on-demand tools.
New Node Created 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 |
orderBy Order By | string | Order By property is required for Pipedream source to identify the entity. We recommend to choose the property represent the created time property of your entity with a variable, for example createdAt. Required |
orderType Order Type | string | The type of the order field. Required |
datetimeFormat Datetime Format | string | The format of the datetime field. E.g. YYYY-MM-DD HH:mm:ss.SSSSZ Required |
nodeLabel Node Label | string | The label of the node. Required |
LIFECYCLE
Event delivery
01
Connect
Your user authorizes Neo4j AuraDB 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
- neo4j_auradb-new-node
- Version
- 0.0.1
- App
- Neo4j AuraDB
- Authentication
- API key
- Delivery
- Polling source
- Output
- Events emitted by Neo4j AuraDB.
- Source
- View on GitHub ↗