onOffice Trigger icon

onOffice Trigger

Polls onOffice for newly created addresses, newly created estates, or modified estates

onOffice Trigger

AI-generated

Overview

This node triggers workflows by polling the onOffice API for new or updated records related to addresses or estates. It supports events for newly created addresses, newly created estates, and updated estates. The node is useful for automating processes that depend on changes in onOffice data, such as syncing contact or property information, sending notifications, or updating databases.

Use Case Examples

  1. Trigger a workflow when a new address is created in onOffice to add the contact to a CRM system.
  2. Trigger a workflow when an estate is updated to refresh property listings on a website.
  3. Poll for new estates created and automatically send a notification email to the sales team.

Properties

Name Meaning
Poll Times Specifies the schedule for polling the onOffice API, including options like every minute, hour, day, week, month, custom cron expressions, or intervals of X minutes/hours.
Event The type of event to trigger on, such as new addresses created, new estates created, or estates updated.
Limit Maximum number of records fetched per poll, with a range from 1 to 500. If more records appear between polls than this limit, the oldest will be missed.
Fields Specifies which fields to return for each record. Different sets of fields are available depending on the event type (address or estate).
Additional Options Optional settings including a filter ID to apply enterprise filters and a flag to format output values for display instead of raw values.

Output

JSON

  • all fields of the fetched records - The node outputs an array of JSON objects representing the newly created or updated addresses or estates, including the requested fields and the tracking field used for polling.

Dependencies

  • Requires an onOffice API key credential for authentication to access the onOffice API.

Troubleshooting

  • If the event parameter is unknown or invalid, the node throws an error indicating an unknown event.
  • If the polling limit is set too low, some records might be missed if many new records appear between polls.
  • Ensure the tracking field is included in the fields to correctly detect new or updated records.
  • If no previous poll timestamp is found, the node returns no data on the first run to avoid duplicate triggers.

Discussion