View as Markdown
MX Technologies icon

MX Technologies TRIGGER

New User Created

Emit new event for each new user created.
  • Trigger
  • Polling
  • API key
  • Webhook delivery

IMPLEMENTATION

Deploy this event source

Connect the user's MX Technologies 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: "mx_technologies-new-user-created",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    mx_technologies: { authProvisionId: "apn_xxxxxxx" },
    timer: { "intervalSeconds": 900 },
  },
  webhookUrl: "https://example.com/webhooks/mx-technologies",
})

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

01

Connect

Your user authorizes MX Technologies 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
mx_technologies-new-user-created
Version
0.0.1
App
MX Technologies
Authentication
API key
Delivery
Polling source
Output
Events emitted by MX Technologies.