View as Markdown
Agrello icon

Agrello TRIGGER

New Document Added to Folder

Emit new event when a user adds a document to a specific folder. See the documentation
  • Trigger
  • Polling
  • OAuth
  • Webhook delivery

IMPLEMENTATION

Deploy this event source

Connect the user's Agrello 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: "agrello-new-document",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    agrello: { authProvisionId: "apn_xxxxxxx" },
    timer: { "intervalSeconds": 900 },
    folderId: "Folder ID",
  },
  webhookUrl: "https://example.com/webhooks/agrello",
})

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 Document Added to Folder configuration
Property Type Description
timer Timer $.interface.timer
Required
folderId Folder ID string
The ID of the folder
Required Dynamic

01

Connect

Your user authorizes Agrello 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
agrello-new-document
Version
0.0.1
App
Agrello
Authentication
OAuth
Delivery
Polling source
Output
Events emitted by Agrello.