Triggers
Automations in Planhat are executed based on triggers. Triggers can be event-driven, scheduled, or initiated via webhooks.
Event-driven Automations
Any data change in Planhat (create, update, delete), as well as manual triggers, can trigger an Automation. Event-driven triggers are configured at the data model level - for example, an update to a Company record can initiate an automation flow. Triggers can respond to changes in specific fields or to general updates, creations, or deletions.
Manual triggers are also defined at the data model level. Each manual trigger can include conditional logic, ensuring that the automation runs only when the defined conditions are met for the triggered object.
Scheduled Automations
Automations can also run on a schedule, and can be configured to run at defined intervals, on specific days, hours and minutes. The following configurations are available:
Every day/week day/day on weekends or specific day of the week
Every hour/second hour/four hours, every hour within business hours (09:00–18:00 GMT) or a specific time in 24-hour period
On the hour/quarter past/half past/quarter to or every 5/10/20/30 minutes
The next run is shown when configuring the Automation.
Webhooks in Automations
Planhat supports webhooks for programmatic integrations via HTTP. Webhooks can function either as triggers (incoming webhooks) or as actions (outbound webhooks) within Automations.
Incoming webhook endpoints support optional filtering at the property level, allowing conditional execution based on evaluated payload data. Security is enforced via unique UUID-based endpoint URLs, HTTPS transport, and optional header/payload validation rules to verify external requests. Only HTTP POST requests with body content are supported for inbound webhooks, ensuring controlled and structured data ingestion.
As an action in Automations, outbound webhooks support HTTP methods (GET, POST, PUT, PATCH, DELETE) and accept dynamic headers and body payloads using replacement tokens. Outbound calls can connect with third-party APIs (including Planhat’s own API) to perform data reads/writes within larger automation flows.
Automations in Planhat are executed based on triggers. Triggers can be event-driven, scheduled, or initiated via webhooks.
Event-driven Automations
Any data change in Planhat (create, update, delete), as well as manual triggers, can trigger an Automation. Event-driven triggers are configured at the data model level - for example, an update to a Company record can initiate an automation flow. Triggers can respond to changes in specific fields or to general updates, creations, or deletions.
Manual triggers are also defined at the data model level. Each manual trigger can include conditional logic, ensuring that the automation runs only when the defined conditions are met for the triggered object.
Scheduled Automations
Automations can also run on a schedule, and can be configured to run at defined intervals, on specific days, hours and minutes. The following configurations are available:
Every day/week day/day on weekends or specific day of the week
Every hour/second hour/four hours, every hour within business hours (09:00–18:00 GMT) or a specific time in 24-hour period
On the hour/quarter past/half past/quarter to or every 5/10/20/30 minutes
The next run is shown when configuring the Automation.
Webhooks in Automations
Planhat supports webhooks for programmatic integrations via HTTP. Webhooks can function either as triggers (incoming webhooks) or as actions (outbound webhooks) within Automations.
Incoming webhook endpoints support optional filtering at the property level, allowing conditional execution based on evaluated payload data. Security is enforced via unique UUID-based endpoint URLs, HTTPS transport, and optional header/payload validation rules to verify external requests. Only HTTP POST requests with body content are supported for inbound webhooks, ensuring controlled and structured data ingestion.
As an action in Automations, outbound webhooks support HTTP methods (GET, POST, PUT, PATCH, DELETE) and accept dynamic headers and body payloads using replacement tokens. Outbound calls can connect with third-party APIs (including Planhat’s own API) to perform data reads/writes within larger automation flows.
Automations in Planhat are executed based on triggers. Triggers can be event-driven, scheduled, or initiated via webhooks.
Event-driven Automations
Any data change in Planhat (create, update, delete), as well as manual triggers, can trigger an Automation. Event-driven triggers are configured at the data model level - for example, an update to a Company record can initiate an automation flow. Triggers can respond to changes in specific fields or to general updates, creations, or deletions.
Manual triggers are also defined at the data model level. Each manual trigger can include conditional logic, ensuring that the automation runs only when the defined conditions are met for the triggered object.
Scheduled Automations
Automations can also run on a schedule, and can be configured to run at defined intervals, on specific days, hours and minutes. The following configurations are available:
Every day/week day/day on weekends or specific day of the week
Every hour/second hour/four hours, every hour within business hours (09:00–18:00 GMT) or a specific time in 24-hour period
On the hour/quarter past/half past/quarter to or every 5/10/20/30 minutes
The next run is shown when configuring the Automation.
Webhooks in Automations
Planhat supports webhooks for programmatic integrations via HTTP. Webhooks can function either as triggers (incoming webhooks) or as actions (outbound webhooks) within Automations.
Incoming webhook endpoints support optional filtering at the property level, allowing conditional execution based on evaluated payload data. Security is enforced via unique UUID-based endpoint URLs, HTTPS transport, and optional header/payload validation rules to verify external requests. Only HTTP POST requests with body content are supported for inbound webhooks, ensuring controlled and structured data ingestion.
As an action in Automations, outbound webhooks support HTTP methods (GET, POST, PUT, PATCH, DELETE) and accept dynamic headers and body payloads using replacement tokens. Outbound calls can connect with third-party APIs (including Planhat’s own API) to perform data reads/writes within larger automation flows.