Adrapid TRIGGER
New Banner Ready
- Trigger
- Polling
- API key
- Webhook delivery
IMPLEMENTATION
Deploy this event source
Connect the user's Adrapid account, configure the source, and choose the webhook where your backend receives events.
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 |
LIFECYCLE
Event delivery
01
Connect
Your user authorizes Adrapid 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
- adrapid-new-banner-ready
- Version
- 0.0.1
- App
- Adrapid
- Authentication
- API key
- Delivery
- Polling source
- Output
- Events emitted by Adrapid.
- Source
- View on GitHub ↗