[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Weekly Loxo recruiting activity report

> Pull last week's Loxo activity by type and recruiter into one summary every Monday, without setting filters and exporting by hand.

Source: https://cotlet.dev/integrations/loxo-api-mcp-server/weekly-recruiting-activity-report

Every Monday the team lead wants calls, submissions and interviews per recruiter, which means opening Reports, setting the filters again and exporting.

Cotlet does it in your own Loxo account with list\_activity and list\_jobs, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=loxo) [All Loxo tools](https://cotlet.dev/integrations/loxo-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can Loxo do this on its own?

Loxo has no reports endpoint in its API reference (checked 22 Oct 2026). Reports live in the Analytics Dashboard, where admins build and export them and set goals; other users see only the reports on a dashboard an admin shared with them.

## How you do it in Loxo today

1. Click the bar chart icon in the left navigation to open the Analytics Dashboard.
2. Open the default Activity Report, set the Date Logged filter to last week, then narrow it with Activity Type, user, Job Pipelines, Companies, Stages or Sources.
3. Save the filters to the report, or use "Save as new" so the original stays as it was.
4. Click the export button in the top right and choose a summary or a detailed report; both come as a CSV.
5. The filters need setting again each week unless the saved report is reused, and non-admins see only reports on a dashboard shared with them.

## How to weekly Loxo recruiting activity report

Prompt

```
Every Monday, summarize last week's Loxo activity by type and by recruiter, and compare it with the week before.
```

1. 01  
### Fix the window  
The agent turns "last week" into a Monday to Sunday range and passes both dates to list\_activity. Loxo filters on Date Logged, so an activity logged late counts in the week it was logged, not the week it happened.
2. 02  
### Read the totals  
list\_activity returns the total, the count per activity type and the count per user for the whole range. The agent builds the summary from these and does not page through every row.
3. 03  
### Compare with the week before  
A second call covers the previous range. The agent flags every activity type that fell and every recruiter whose count halved.
4. 04  
### Drill into one type  
When you ask who submitted whom, the agent repeats the call with activity\_type set to Submission and follows next\_cursor through the rows.
5. 05  
### Name the jobs  
list\_jobs turns the job ids on those rows into job titles, so the report names pipelines, not numbers.

### What you get back

Example data

```
Oct 12 to Oct 18: 48 activities (previous week: 61)
Outgoing Call 21, Moved to Interviewing 12, Scheduled Interview 9, Submission 6
Dana Reyes 30, Sam Okafor 18
Down most: Outgoing Call (-14)
```

### Other ways to ask

- Send me every Friday the submissions per job for this week.
- Which recruiter logged the fewest outgoing calls this month?
- Compare this quarter's scheduled interviews with last quarter's.

## What Loxo allows, and what to know first

- By default only account admins create and edit reports and goals; other users need a Group permission and a dashboard shared with them.
- The Activity Report filters on Date Logged, Activity Type, the user who logged it, Job Pipelines, Companies, Stages and Sources.
- A candidate dragged between stages appears as "Moved to ...", and a trigger pick adds a second event, so counts per type include both unless you filter one.
- Loxo exports a report only after its filters are saved, and Executive Presentations export as PDF only, while other reports export as CSV.

Every tool here only reads, so it can run weekly from n8n, Make, Zapier or cron without waiting for your OK.

Sources: [Loxo Help: Reporting Questions](https://help.loxo.co/en/articles/9027502-reporting-questions) · [Loxo Help: Loxo's Analytics Dashboard](https://help.loxo.co/en/articles/8386308-loxo-s-analytics-dashboard) · [Loxo Help: Legacy Reports](https://help.loxo.co/en/articles/3082958-reporting-101) · [Loxo API reference](https://loxo.readme.io/reference/loxo-api)

## Call list\_activity from a script

curl

```
curl "https://cotlet.dev/api/v1/loxo/activities?date_from=2026-10-12&date_to=2026-10-18" \
  -H "Authorization: Bearer $COTLET_API_KEY"
```

Example response

```
{
"date_from": "2026-10-12",
"date_to": "2026-10-18",
"total": 48,
"by_type": [
{
"activity_type": "Outgoing Call",
"count": 21
},
{
"activity_type": "Moved to Interviewing",
"count": 12
},
{
"activity_type": "Scheduled Interview",
"count": 9
},
{
"activity_type": "Submission",
"count": 6
}
],
"by_user": [
{
"user": "Dana Reyes",
"count": 30
},
{
"user": "Sam Okafor",
"count": 18
}
],
"activities": [
{
"logged_at": "2026-10-18T16:40:00Z",
"activity_type": "Submission",
"user": "Dana Reyes",
"person": "Tom Becker",
"job_id": 2481530
},
{
"logged_at": "2026-10-18T11:02:00Z",
"activity_type": "Outgoing Call",
"user": "Sam Okafor",
"person": "Lena Ortiz",
"job_id": 2481544
}
],
"next_cursor": "c2"
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is loxo\_read → list\_activity. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/loxo-api-mcp-server.md#automations)

## Loxo tools this automation uses

__Cotlet Loxo tools used to weekly Loxo recruiting activity report__
| Tool | Parameters |
| -------------- | ------------------------------------------------------------------ |
| list\_activity | date\_from, date\_to, activity\_type, user, job\_id, stage, cursor |
| list\_jobs | query, cursor |

[All 12 Loxo tools with descriptions](https://cotlet.dev/integrations/loxo-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect Loxo to Cotlet?

Yes. You sign in to Loxo yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Loxo once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

## More Loxo automations

- [Log interview outcomes in Loxo and move candidates](https://cotlet.dev/integrations/loxo-api-mcp-server/log-interview-outcomes.md)
- [Email every candidate in a Loxo pipeline stage](https://cotlet.dev/integrations/loxo-api-mcp-server/email-candidates-in-a-pipeline-stage.md)
- [Loxo API and MCP server: every tool](https://cotlet.dev/integrations/loxo-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Loxo.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Loxo.

[Sign up free](https://cotlet.dev/app/signup?app=loxo)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.