Skip to content

Latest commit

 

History

History
33 lines (28 loc) · 15.1 KB

triggereventrequestdto.md

File metadata and controls

33 lines (28 loc) · 15.1 KB

TriggerEventRequestDto

Example Usage

import { TriggerEventRequestDto } from "@novu/api/models/components";

let value: TriggerEventRequestDto = {
  name: "workflow_identifier",
  overrides: {},
  payload: {},
  to: [
    {
      topicKey: "<value>",
      type: "Topic",
    },
  ],
};

Fields

Field Type Required Description Example
actor components.Actor It is used to display the Avatar of the provided actor's subscriber id or actor object.
If a new actor object is provided, we will create a new subscriber in our system
bridgeUrl string N/A
controls components.Controls N/A
name string ✔️ The trigger identifier of the workflow you wish to send. This identifier can be found on the workflow page. workflow_identifier
overrides components.TriggerEventRequestDtoOverrides This could be used to override provider specific configurations {
"fcm": {
"data": {
"key": "value"
}
}
}
payload components.TriggerEventRequestDtoPayload The payload object is used to pass additional custom information that could be used to render the workflow, or perform routing rules based on it.
This data will also be available when fetching the notifications feed from the API to display certain parts of the UI.
{
"comment_id": "string",
"post": {
"text": "string"
}
}
tenant components.Tenant It is used to specify a tenant context during trigger event.
Existing tenants will be updated with the provided details.
to components.To[] ✔️ The recipients list of people who will receive the notification.
transactionId string A unique identifier for this transaction, we will generated a UUID if not provided.