View as Markdown
Rumi AI icon

Rumi AI TRIGGER

New Session Completed

Emit new events when a session is completed. See the documentation
  • Trigger
  • Polling
  • OAuth
  • Webhook delivery

IMPLEMENTATION

Deploy this event source

Connect the user's Rumi AI 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: "rumi_ai-new-session-completed",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    rumi_ai: { authProvisionId: "apn_xxxxxxx" },
    timer: { "intervalSeconds": 900 },
  },
  webhookUrl: "https://example.com/webhooks/rumi-ai",
})

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 Session Completed configuration
Property Type Description
timer Timer $.interface.timer
Required

01

Connect

Your user authorizes Rumi AI 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
rumi_ai-new-session-completed
Version
0.0.1
App
Rumi AI
Authentication
OAuth
Delivery
Polling source
Output
Events emitted by Rumi AI.