View as Markdown
Lamini icon

Lamini TRIGGER

New Job Status

Emit new events with the status of a training job. See the documentation.
  • Trigger
  • Polling
  • API key
  • Webhook delivery

IMPLEMENTATION

Deploy this event source

Connect the user's Lamini 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: "lamini-get-job-status",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    lamini: { authProvisionId: "apn_xxxxxxx" },
    timer: { "intervalSeconds": 900 },
    jobId: "Job ID",
  },
  webhookUrl: "https://example.com/webhooks/lamini",
})

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 Job Status configuration
Property Type Description
timer Polling Schedule $.interface.timer
How often to poll the API
Required
jobId Job ID string
The ID of the fine-tuning job to use.
Required Dynamic

01

Connect

Your user authorizes Lamini 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
lamini-get-job-status
Version
0.0.2
App
Lamini
Authentication
API key
Delivery
Polling source
Output
Events emitted by Lamini.