What it does
Visitor actions since an exclusive timestamp, oldest first. since, and since_id from next when a page is full, page through the events, for mirroring calls into the site's own log. Each event has op (insert, update, or delete), the row and its changes; row values can hold text that visitors typed. Omit since to start at the oldest stored entry. The worker deletes rows older than action_log_retention_days (90), so this feed only reaches back that far. When the owner set the site's Webhook with visitor actions on, each action is also sent to it.
Plans
Works on every plan: Free, Basic, Pro and Ultra.
Parameters
| Name | Type | About |
|---|---|---|
site_idrequired | string | The id of the site. list_sites gives the ids of your sites. |
since | string | Returns events after this time, oldest first. Leave it out to start at the oldest stored event. |
since_id | string | With since: the id from next, so events at the same time aren't skipped. |
limit | integer | How many events to return. |
cursor | string | next_cursor from the previous page of this tool, to read the next page. Send the other arguments as on the first call; leave out the paging arguments the cursor replaces. |
Example
Call action_events with these arguments:
{
"site_id": "01a1…",
"limit": 50
}
Ids like 01a1… stand for your own. list_sites and list_tables give you the real ones.
Related guides
- What visitor actions areNamed, limited changes people make from a page.
- Tick, edit, add and deleteThe kinds of action, and when to use each.