View as Markdown
Concord icon

Concord TRIGGER

New Agreement with Status

Emit new event for new agreements with the specified status(es) See the documentation
  • Trigger
  • Polling
  • API key
  • Webhook delivery

IMPLEMENTATION

Deploy this event source

Connect the user's Concord 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: "concord-new-agreement-with-status",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    concord: { authProvisionId: "apn_xxxxxxx" },
    timer: { "intervalSeconds": 900 },
    organizationId: 10,
  },
  webhookUrl: "https://example.com/webhooks/concord",
})

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 Agreement with Status configuration
Property Type Description
timer Timer $.interface.timer
Required
organizationId Organization ID integer
Select an Organization from the list, or provide a custom Organization ID. See the documentation if needed.
Required Dynamic
statuses Status(es) string[]
One or more statuses to emit events for. If none are selected, events will be emitted for all statuses.
Optional
search Filter by search pattern string
If set, events will only be emitted for agreement matching the specified pattern
Optional

01

Connect

Your user authorizes Concord 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
concord-new-agreement-with-status
Version
0.0.1
App
Concord
Authentication
API key
Delivery
Polling source
Output
Events emitted by Concord.