interlocute.ai beta
Create a node

Scheduling & Triggers

Make your AI nodes proactive. Schedule recurring tasks, trigger execution from events, and automate intelligence workflows — all managed by the platform.

Try Interlocute Read the docs

What are triggers?

Triggers let your AI nodes run on a schedule or in response to events, rather than waiting for a user to send a message. A scheduled trigger fires at defined intervals (daily, hourly, custom cron). This transforms your node from a reactive chat endpoint into a proactive intelligence agent.

Why it matters

Many AI use cases are not conversational — they are operational. Daily briefings, periodic data analysis, automated report generation, and monitoring tasks all require the AI to act without a human prompt. Triggers make this possible without external cron infrastructure.

Managed infrastructure

Triggers are managed by Interlocute's infrastructure — reliable, logged, and observable. Unlike a fragile cron script on a VM, scheduled triggers have built-in retry logic, failure logging, and governance. They are first-class platform objects, not afterthoughts.

Composable with all features

Triggered executions have access to the same node capabilities as interactive calls: memory, RAG, tool use, and streaming. A scheduled task can retrieve context from memory, query a knowledge base, call an external API, and deliver results to Slack or email.

Frequently Asked Questions

Scheduling & Triggers

What are triggers in Interlocute?
Triggers allow your AI node to execute on a defined schedule (cron-style) or in response to events, rather than waiting for a user message. This makes nodes proactive — they can generate reports, monitor data, and send notifications automatically.
How do I set up a scheduled trigger?
Configure a trigger through the dashboard or API by specifying a cron expression and an optional input message. The platform executes your node at the specified intervals and logs every invocation with its result.
Are triggers reliable?
Yes. Triggers are managed infrastructure with built-in retry logic, failure logging, and observability. They are more reliable than self-hosted cron jobs because the platform handles scheduling, execution, and error recovery.
Can a triggered execution use memory and RAG?
Yes. Triggered executions have access to all node features — memory, RAG, tool use, and streaming. A scheduled task can retrieve past context, query a knowledge base, and call external tools just like an interactive conversation.
How are triggered executions billed?
Triggered executions are billed the same way as interactive requests — based on token usage. Each scheduled invocation consumes tokens and is recorded in your usage ledger with the trigger as the source.
Can I view the history of trigger executions?
Yes. Every trigger execution is logged with timestamps, input, output, token usage, and any errors. You can review trigger history through the dashboard or query it via the API.

Documentation

Triggers Guide API Reference

Related Features

Agent Deployment

Deploy AI agents as stable, addressable endpoints in seconds. No infrastructure to manage, no containers to orchestrate.

Observability & Logging

Built-in logging, tracing, and token usage visibility for every node call. Understand exactly what your AI is doing and what it costs.

Tool Use & Function Calling

Let your AI nodes call external tools and APIs. Pre-configured function calling with governed execution, built into the runtime.

Ready to build with Scheduling & Triggers?

Deploy your node in seconds and start using Scheduling & Triggers today.

Try Interlocute Read the docs