Hyperise TRIGGER
New Image Impression
- Trigger
- Polling
- API key
- Webhook delivery
IMPLEMENTATION
Deploy this event source
Connect the user's Hyperise 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: "hyperise-new-image-impression",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
hyperise: { authProvisionId: "apn_xxxxxxx" },
timer: { "intervalSeconds": 900 },
imageTemplateHash: "Image Template Hash",
},
webhookUrl: "https://example.com/webhooks/hyperise",
})
console.log(deployed.id)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/triggers/deploy \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "hyperise-new-image-impression",
"webhook_url": "https://example.com/webhooks/hyperise",
"configured_props": {
"hyperise": { "authProvisionId": "apn_xxxxxxx" },
"timer": { "intervalSeconds": 900 },
"imageTemplateHash": "Image Template Hash"
}
}'MCP servers expose Hyperise actions as on-demand tools.
New Image Impression is an event source, so your application deploys it
with the Connect SDK or API and then either receives each event at a
webhook URL or retrieves events on demand with the trigger events API.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.
| Property | Type | Description |
|---|---|---|
timer Timer | $.interface.timer | Required |
imageTemplateHash Image Template Hash | string | The image hash of the template to use Required Dynamic |
LIFECYCLE
Event delivery
01
Connect
Your user authorizes Hyperise 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.
REFERENCE
Trigger details
- Registry key
- hyperise-new-image-impression
- Version
- 0.0.1
- App
- Hyperise
- Authentication
- API key
- Delivery
- Polling source
- Output
- Events emitted by Hyperise.
- Source
- View on GitHub ↗