Skip to main content
A follow-up is a wait with a place to look and a deadline. “The site emailed a code”, “the recruiter will send the offer letter”, “the export is ready in ten minutes”: an agent records what it is waiting for and where it will land, Valendata watches that place, and the agent carries on when the thing arrives or the time is up. You can make follow-ups from:
  • The app: Igris and your in-app agents make them as they work, and are woken in their own chat when the thing comes.
  • The API: the Follow-ups routes.
  • AI assistants: the follow-up MCP tools. See MCP tools.
A follow-up made through the API or an assistant wakes nobody. You create it, then read it back with Get a follow-up (or get_followup) until it has ended.

​
Wait, or check back

A check-back is a follow-up whose place is time.

​
Where things can land

Give a mailbox address and Valendata works out whether it is your Valendata inbox or a connected mail app. A place in a connected app needs that app connected; otherwise the answer is app_not_connected with the link that connects it.

​
What counts as arrived

match says what you are waiting for and who it should come from. Every field you give must hold; the ones you leave empty are not checked. Three rules are built in and cannot be switched off:
  • Only things that arrive after the follow-up was made count. An old code in the mailbox never matches.
  • The agent is handed only the thing it waited for: the code, the link, the file, or a short excerpt. Never the rest of the mailbox.
  • A place in a connected app is read as you, with your own connection, and only with tools that read. A follow-up never sends or changes anything.

​
What you get back

Each follow-up has a status: waiting, done, cancelled, or failed (it could not be checked, for example the app was disconnected; note says why). Once it is done, outcome says how (found, time_up, expired) and found holds what arrived: its kind, a one-line summary, and the code, link, file_url, or text. The fields are on Get a follow-up.

​
Limits

  • Waiting at once: up to 25 per account. Cancel one to make room.
  • How long: up to 72 hours each. After the deadline a wait ends as expired.
  • How often: check_every is at least 30 seconds. Leave it out for what suits the place; an inbox and a run are told on arrival and need no polling.

​
Credits

Watching your Valendata inbox, a web page, a run, or the time is free. Each check that reads a connected app (email_app, app_tool) is an app call and costs the app-call price, the same as reading the app yourself (see Connected apps). A wait of two hours that checks every minute is 120 calls, so choose check_every with that in mind. Every call is listed under Activity on the Integrations page. An API key or an AI assistant needs followups:read to see follow-ups and followups:write to create or cancel them, plus apps:read for a place in a connected app. For an assistant all of them are opt-in. See Authentication and scopes.