Skip to main content
Lobyco publishes an Inbound API trigger event when an Inbound API block is created, changed, published, stopped or deleted in Lobyco Nexus. Each event carries the block’s name and the URL your system calls to start its flow. Your system can use them to keep its list of Inbound API endpoints up to date by itself.
Events can arrive out of order. Keep, for each triggerId, the event with the latest time of change. That is updatedAt, publishedAt, stoppedAt or deletedAt, whichever the event carries, and createdAt on a created event.An event can be lost. If Lobyco cannot publish an event, it does not try again, and the change in Nexus still stands. The block’s next change publishes its whole state again.

​
Field reference

Your endpoint receives these events through a subscription in Data streams in Nexus, under the event types below. Unless the subscription transforms the payload, the request body is the payload the schemas describe, with no envelope around it. In the payload, the Inbound API block is called a trigger. triggerId is the block’s id, and the last segment of its url.
  • Every event carries the block’s whole state after the change. You never combine events to know what a block looks like.
  • A save that changes nothing publishes nothing. Dates are compared to the second.
  • One save can publish two events. A save that changes the details and publishes or stops the block publishes Trigger Updated first. Creating a published block publishes Trigger Created, then Trigger Published. Both events share the time of the change, and their eventId values differ in the event name.
  • A pasted copy is unpublished, so copying a block publishes Trigger Created alone.
  • Who made the change, and when, is named after the change. Trigger Updated carries updatedBy and updatedAt, Trigger Published carries publishedBy and publishedAt, and so on. createdBy and createdAt are on every event.
  • Whether the block is active is not sent. The block accepts calls while isPublished is true and the current time is between startDate and endDate. Work it out on your side.
  • Deleting a campaign publishes no events. Nexus lets an admin user delete a campaign only once its blocks are gone, and each block deletion publishes Trigger Deleted.
  • A block last saved before Lobyco released these events publishes nothing until its next save.
The payloads follow the same conventions as the campaign events:
  • Property names are camelCase, such as triggerId and eventId.
  • A property with no value is left out of the payload, not sent as null. Only description, url, startDate and endDate can be absent.
  • Dates are UTC with second precision, in the form yyyy-MM-ddTHH:mm:ssZ. The time inside eventId is the exception. It is written to the tick, as yyyy-MM-ddTHH:mm:ss.fffffff, so two saves within one second still get different ids.

​
Schemas

Last modified on November 5, 2026