Automation for hiring · Runs 1 day before a meeting with someone outside your organization
Attendee research
A research briefing on outside attendees before tomorrow's meetings. Your assistant runs it 1 day before a meeting with someone outside your organization and tells you when something needs your attention.
Attendee research — Sep 17
Automation run • Sep 17
Attendee research
Output
Briefing for tomorrow's interview with Dara Finch, candidate for the senior ecommerce engineer role at Harbor & Pine.
Meeting: Friday, September 18, at 10:00 AM Portland time (video call).
- Attendees: Juno Pell (recruiting lead), Ezra Holt (engineering hiring manager), and Dara Finch (external candidate).
- Background: Dara Finch is a senior frontend and full stack engineer based in Portland. Experience centers on custom storefronts and web performance. Application materials were received on September 10 and saved to Google Workspace.
- Email history: Juno sent interview availability on September 12. Dara confirmed the time on September 13 and shared a link to code samples.
- Shared files: Dara Finch Resume.pdf in Google Workspace Drive. Senior Ecommerce Engineer Scorecard shared internally with Ezra Holt.
- Candidate context: Dara brings seven years of commerce platform experience. Current employer news shows no executive changes or funding events in the last 90 days. Ezra noted an interest in discussing Dara's work with catalog sync logic.
No matching contact record was found in HubSpot.
Automation steps. Your assistant follows these 3 steps each time it runs, using your connected email and calendar.
- 01
A day before each external meeting, research every attendee from outside my organization: their role and background, my email history with them, their company's recent news, and any shared documents.
- 02
Skip internal-only meetings, which you can tell from the attendees' email domains.
- 03
Pull it into one structured briefing per meeting, as deep as that meeting warrants.
Adjust the automation in chat
Tell your assistant what to do differently and it sets up that version for you.
- Only prepare briefings for candidate interviews and skip vendor meetings.
- Deliver the briefing an hour before the meeting instead of a day ahead.
- Include open CRM notes from HubSpot whenever an attendee matches an existing contact.
Results arrive as a message from your assistant. Each run posts to your conversation with your assistant, and can email you too. The automation keeps a log in your knowledge base and reads it before each run to see what has changed.
What starts this automation
Runs 1 day before a meeting with someone outside your organization. When you add it, choose the lead time and which meeting titles to match.
Only useful reports
When nothing needs attention, the run says so in a line or stays quiet. When there are findings, you get them with a link to the full run.
What it does on its own
Researches attendees and writes the briefing on its own. Changes nothing. An automated run has no tool that sends, posts, shares, or deletes anything.
This automation reads your email and calendar. Connect Google Workspace or Microsoft 365 to Fieldwork. The automation uses whichever you connect. It also uses your files, CRM when connected.
More automations for hiring.
Questions about this automation.
- How do I set this up?
- Open your assistant on the Agents page in Fieldwork, locate Attendee research in the job library, and click Add. If your Google Workspace or Microsoft 365 account is not linked yet, the setup card prompts you to connect it before saving. It begins checking for upcoming meetings 1440 minutes in advance, which you can adjust during setup.
- What does it do on its own versus waiting for me?
- It reads your calendar, inspects connected files, searches email history, and compiles the briefing without taking external actions. It never contacts attendees, deletes records, or modifies events on your calendar.
- Where do the briefings arrive?
- Each briefing appears as a message directly in your chat with your assistant and can also be sent to your email. If a day has no external meetings on your calendar, it stays quiet.
- How does it tell if an attendee is from outside the organization?
- It reviews the email addresses on each calendar invite against your company domain. Invitations that contain only internal team members are skipped automatically.
Security first
No training on your data
Neither we nor our model providers train on your data. Inference runs with zero retention wherever the provider supports it.
Access
Agents only see what the person asking can see. Conversations, files, apps and connections stay private until shared, and admins have no way into conversations.
Encryption and isolation
Data is encrypted at rest and in transit. Each user's code runs in its own microVM, and secrets reach models by name only.
Continuity
Continuous backups, replicated to a second region. Data is exported on request and deleted within 30 days of a contract's end.