Connectors
The handbook and the people tools, in one project.
- Notion, Google and Microsoft through existing connectors.
- Payroll and HR tools from their API docs.
- Signed forms by email.
Anyone asks in Claude and gets the answer with the policy passage cited.
Ask your own balance from your own AI, on a server built to answer per person.
Offer letters and agreements read into a table: dates, terms and obligations you can ask about.
A workflow runs the checklist across your tools, with an approval step wherever a person should decide.
Both kept current and joined in one question.
Connectors
Context layer
Workflows, Alerts & Surfaces
Every plan has unlimited users, so everyone asks the handbook from their own AI before the question reaches HR.
Recorded exit interviews are transcribed, and you ask across them with the passages used.
A saved question checks the agreements table each week and starts a reminder when a trial period or contract is about to end.
Export the onboarding workflow with everything it needs, and install it for the next team or location.
An employee's offer letter, payroll row and HR record answer as one person, with any guessed match put to you to confirm.
Connect it and ask the question you answered most last week.
Security
4 calls mention exporting
From 18 research calls · passages cited
Maya Chen
“I export to Excel every Friday.”
Every research call, there to ask
Which orders are stuck today?
SO-4471 · stuck 3 days
Halden Group · promised Oct 18
No shipping label
ShipStation · waiting on stock
The stuck order, found first
Why did we miss the month?
September revenue
$412,000 of $460,000
Pipeline
HubSpot · 2 deals moved to October
One answer across the business
Yes. Roles decide which HR data stores and fields each person can see, so salaries or Social Security numbers can be hidden or partly masked for everyone outside HR. To show each employee only their own records, add a Check Access step that filters by who is signed in.
Yes, in your data stores. altspark flags fields that look like personal data, such as email, phone, Social Security number, date of birth, bank account or card number, by their names and their values, and suggests masking them. Once you accept, you choose for each role whether that field shows its real value, part of it, or nothing. Database connections are always read-only.
Only through a step you build for it, and you can require approval first. altspark never writes to databases, and every workflow run is logged.
Book a demo and bring your handbook.