View as Markdown
Raven Tools icon

Raven Tools TRIGGER

New Keyword Added

Emit new event for each keyword added to a domain See docs here
  • Trigger
  • Polling
  • API key
  • Webhook delivery

IMPLEMENTATION

Deploy this event source

Connect the user's Raven Tools 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: "raven_tools-keyword-added",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    raven_tools: { authProvisionId: "apn_xxxxxxx" },
    timer: { "intervalSeconds": 900 },
    domain: "Domain",
  },
  webhookUrl: "https://example.com/webhooks/raven-tools",
})

console.log(deployed.id)

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.

New Keyword Added configuration
Property Type Description
timer Timer $.interface.timer
Required
domain Domain string
The domain to watch for new keywords.
Required Dynamic

01

Connect

Your user authorizes Raven Tools 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.

Registry key
raven_tools-keyword-added
Version
0.0.1
App
Raven Tools
Authentication
API key
Delivery
Polling source
Output
Events emitted by Raven Tools.