Actions are quite different from Activities. While activities represent events or tasks throughout a job seeker's search (Applications, Meetings, Interviews, etc), an action is logged any time a job seeker does something within the Huntr platform. You can think of it as a full historical log of everything each job seeker did within Huntr, from a job being created, to a note being updated, to an activity being deleted, we log it all as actions.

As an example, say a job seeker saves 15 jobs to the Wishlist stage in their board, but only applies (and drags) one of those jobs to the application stage. When you look at actions in your portal, you will notice this job seeker has 15 JOB_CREATED actions, 1 JOB_MOVED action, and 1 ACTIVITY_CREATED for the application activity created. If you look at the job seeker's Activities, they will only have 1 Apply activity logged.

As seen in the example above, actions can get very verbose. As such, actions are great for tracking job seeker engagement, building powerful integrations between Huntr and other systems (see Webhooks ), or doing deep dives into your job seeker's data and their use of Huntr. For day-to-day highlights, we suggest sticking with looking at core Activities like Applications, Interviews and Offers Received.

A table of actions, as seen from the Actions view in the advisor portal.