Grimp
HRConnect AI agents to Grimp, an education partner platform for school career services. Agents manage student records, publish job posts, confirm recruitment outcomes, and tag the contacts and enterprises behind each employer relationship.
What This Integration Enables
A school's career services team is running two businesses at once. One is a caseload of named young people whose employability the institution is accountable for. The other is a commercial pipeline of employers, mandates and apprenticeship-tax relationships that funds the first. Grimp puts both in one system, and this connector is worth building on precisely because an agent can work across that seam, which is where the manual effort actually sits.
On the learner side, agents list and read students with their profile, campus, class, year, work situation, tags, referent coaches and hiring details. They invite new learners with an onboarding email, update profile fields, deactivate and reactivate access, upload documents with a typed category and upload a resume as the learner's active CV, and record a confirmed hiring against a specific admission application. On the job board, they publish, update and archive job posts with contract types, target programs and diplomas, remote policy and a publisher contact, and read the applications each post received. On the commercial side, they create, read, update and permanently delete enterprise opportunities with type, pipeline status, monetary value and target date, and push admission leads captured from a form. Reference data comes from List Campuses And Programs, List Sectors, List Admission Statuses and List Admission Statuses By Pipeline, and a full tag vocabulary can be listed, created, renamed and deleted per category.
Two limits are worth stating rather than glossing. The CRM records themselves, contacts and enterprises, are readable and taggable but not writable through this surface: there is no create or update for either, so a flow reads them, classifies them with tags, and does its record-keeping about employers on the opportunity object. And several operations replace rather than merge. Update Student replaces the tag and referent sets it is given, Replace Opportunity Tags, Replace Contact Tags and Replace Enterprise Tags replace every tag on the record, and Delete Tag removes a tag from every record it was assigned to across the school. Grimp exposes no webhook subscription endpoints (outbound webhooks are configured inside the Grimp interface), so this connector ships no trigger and a flow that needs to notice new applications or status changes polls List Applications, List Students or List Opportunities on a schedule.
Without FlowRunner
With FlowRunner
Use Case Scenarios
An employer offer that becomes a real job post
An employer submits an offer through a Typeform intake form. The agent reads List Campuses And Programs to resolve the programs and diplomas the post should target, List Sectors to classify the employer, and List Tags to pick the job-post tags in use. It then calls Create Job Post with the title, description, hiring company, expiry date, contract types and publisher contact. It applies the tags with Add Job Post Tags and confirms the post is visible to the intended campuses. What used to be a retyped email with guessed programs becomes a post built from resolved reference data.
Cohort placement reporting that stays current
Career services need to know where a cohort stands. On a schedule the agent pages List Students filtered by campus, class and year, reads each learner's work situation (To Place, Opportunity or Placed), pulls List Applications for the same filters, and writes the joined picture into Google Sheets or a reporting board. Learners sitting in To Place with no applications for several weeks are surfaced to their referent coach by name rather than discovered at the end of term.
A learner who has gone quiet
A learner stops logging in and stops applying. The agent notices the gap from List Applications and Get Student, checks the referent coaches on the record, and raises it to the named coach with the learner's current work situation, tags and application history attached. It does not call Disable Student, because deactivating a learner ends their access to the platform they are meant to be job hunting on, and that is a pastoral decision rather than a data-hygiene one. The agent's job here is to make the silence visible early.
Human-in-Loop Highlight
Confirm Student Recruitment is where this connector stops and asks, because it is the operation that turns a document into an institutional claim. Calling it records the hiring company name and SIRET, the job title and the contract type against a specific admission application, and marks that learner as placed. Placement is not internal bookkeeping for a school: it is the number the institution reports, and it is tied to a real contract for work-linked training. Correcting a wrong SIRET or a wrong contract type after the fact is a manual repair that has to travel through whoever consumed the figure. The API also constrains the contract type to Work-Linked Training or Internship, so a placement that is neither has no honest representation here at all, which is exactly the case a machine should escalate rather than round off. The agent therefore does the extraction and hands over the judgment. It posts to the referent coach or career services advisor: "[Learner name] appears to have signed with [employer], SIRET [number], as [job title], contract type [type], against admission application [reference]. Source document attached. Confirm the placement, correct a field, or tell me this is not a placement we record." On approval the agent calls Confirm Student Recruitment and files the contract with Add Student Document under the contract category. The reading, matching and document handling run unattended. Declaring a young person placed does not.
Agent Capabilities
48 actionsAccount and Reference Data
5- Get Current Account Returns the administrator account associated with the API token, including the user id, name and email. Useful for verifying that the token is valid and identifying the connected school.
- List Campuses And Programs Returns every campus for the school along with its classes and academic years, including their ids and references. Use these values to target students and job posts by campus, class or year.
- List Sectors Returns the list of industry sectors available on the school's Grimp workspace, each with its id and label. Sectors can be referenced when qualifying enterprises and opportunities.
- List Admission Statuses Returns the admission (pipeline) statuses configured for the school, each with its id, label and type. These statuses describe where a student's admission application sits in the recruitment pipeline.
- List Admission Statuses By Pipeline Returns the admission statuses configured for the school grouped by pipeline, with each pipeline's id, name and ordered list of statuses.
Students
14- List Students Returns a paginated list of students (learners) for the school with their profile, campus, class and year, work situation, tags and hiring details. Optional filters narrow results by campus, class, year or email.
- Get Student Returns the full profile for a single student by id, including contact details, admission applications, documents, tags, referent coaches and hiring information.
- Invite Student Invites a new student (learner) to Grimp by email, creating their record and sending an onboarding invitation. First name, last name and email are required. Optionally assigns campus, class, year, phone, an external id and referent coaches.
- Update Student Updates an existing student's profile fields by id. Only provided fields are changed, but tags and referents provided here REPLACE the existing sets, and an empty list clears them. Work situation must be one of To Place, Opportunity or Placed.
- Disable Student Deactivates a student by id, preventing any further login and hiding them from the students list. The record is retained and can be restored with Reactivate Student.
- Reactivate Student Reactivates a previously deactivated student by id, restoring their access and visibility in the students list.
- Confirm Student Recruitment Confirms the recruitment of a student for a specific admission application, recording the hiring company name and SIRET, job title and contract type. This marks the learner as placed for that application, and it is the action routed for human sign-off.
- List Student Documents Returns the documents attached to a student by id, each with its title, document type, file URL and timestamps.
- Add Student Document Uploads a document file to a student's record, with a title and a document type such as CV, diploma or contract. Optionally assigns the document to one or more admission applications.
- Add Student Resume Uploads a resume file for an existing student. The resume becomes the student's active CV on Grimp, pending validation.
- Add Student Tags Adds tags to a student, keeping any existing tags. Provide existing tag ids or tag labels; labels that do not yet exist are created and then assigned.
- Remove Student Tags Removes tags from a student. Provide the tag ids or tag labels to remove; other tags are left in place.
- Add Student Referents Adds referent coaches to a student, keeping existing ones. Each referent is identified by the coach's email or id.
- Remove Student Referents Removes referent coaches from a student. Each referent is identified by the coach's email or id.
Job Posts
7- List Job Posts Returns a paginated list of job posts published on the school's internal job board, each with title, contract type, company, dates and applications. Optional filters narrow by external id, company name, URL or title.
- Get Job Post Returns a single job post by id, including its full description, contract type, company details, dates and the list of applications received.
- Create Job Post Creates a job post and publishes it on the school's internal job board. Title, description, hiring company name, expiry date, contract types, target programs and diplomas, and a publisher user object are required.
- Update Job Post Updates an existing job post by id. Title, description, hiring company name, expiry date, contract types and the publisher user object are required by the API. Optional fields adjust location, remote policy, salary, tags and campus visibility.
- Archive Job Post Archives a job post by id, removing it from the active job board while retaining the record.
- Add Job Post Tags Adds tags to a job post, keeping existing tags. Provide existing job-tag ids or tag labels; labels that do not yet exist are created and assigned.
- Remove Job Post Tags Removes tags from a job post by tag ids or tag labels; other tags are left in place.
Opportunities
8- List Opportunities Returns a paginated list of business opportunities such as mandates, partnerships or apprenticeship-tax deals, each with type, status, value, target date and linked enterprise.
- Get Opportunity Returns a single opportunity by id, including its type, status, value, target date, linked enterprise and tags.
- Create Opportunity Creates a business opportunity linked to an enterprise. Name and enterprise id are required. Optionally set the opportunity type, pipeline status, monetary value and a target date.
- Update Opportunity Updates an existing opportunity by id. Only provided fields are changed. Type and status must be one of the documented values.
- Delete Opportunity Permanently deletes an opportunity by id.
- Add Opportunity Tags Adds tags to an opportunity, keeping existing tags. Labels that do not yet exist are created and then assigned.
- Remove Opportunity Tags Removes tags from an opportunity by tag ids or tag labels; other tags are left in place.
- Replace Opportunity Tags Replaces ALL tags on an opportunity with the provided set of opportunity-tag ids. Send an empty list to clear every tag.
CRM
9- List Applications Returns a paginated list of student job applications across the school, optionally filtered by campus, class, year or student email.
- List Contacts Returns a paginated list of CRM contacts associated with students, optionally filtered by campus, class, year or email. Read only apart from tagging.
- List Enterprises Returns a paginated list of enterprises (companies) associated with students, optionally filtered by campus, class, year or email. Read only apart from tagging.
- Add Contact Tags Adds tags to a CRM contact, keeping existing tags. Labels that do not yet exist are created and assigned.
- Remove Contact Tags Removes tags from a CRM contact by tag ids or tag labels; other tags are left in place.
- Replace Contact Tags Replaces ALL tags on a CRM contact with the provided set of contact-tag ids. Send an empty list to clear every tag.
- Add Enterprise Tags Adds tags to a CRM enterprise, keeping existing tags. Labels that do not yet exist are created and assigned.
- Remove Enterprise Tags Removes tags from a CRM enterprise by tag ids or tag labels; other tags are left in place.
- Replace Enterprise Tags Replaces ALL tags on a CRM enterprise with the provided set of enterprise-tag ids. Send an empty list to clear every tag.
Leads
1- Create Lead Creates a new admission lead (prospective student) on Grimp. First name, last name, source, form name, locale and a data object with the captured form fields are required. Optionally attaches an email, campus, phone and external id.
Tags
4- List Tags Returns all reference tags of a given category (Student, Job Post, Opportunity, Contact or Enterprise) configured for the school, each with its id and label.
- Create Tag Creates a new reference tag of a given category with the provided label. The created tag can then be assigned to records of that category.
- Update Tag Renames an existing reference tag of a given category by id. Records already carrying the tag keep it with the new label.
- Delete Tag Permanently deletes a reference tag of a given category by id, removing it from every record it was assigned to across the school.
Frequently Asked Questions
What can FlowRunner do with Grimp?
FlowRunner agents can run Get Current Account, List Campuses And Programs, and List Sectors in Grimp, plus 45 more actions.
Does connecting Grimp to FlowRunner require OAuth?
No. Grimp connects to FlowRunner with an API key, no OAuth flow required.
Can Grimp trigger a FlowRunner workflow automatically?
Grimp doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Grimp
$100 in credits. No card required. Connect in minutes.