Xenition is an AI workspace with 23 real editing surfaces — document, spreadsheet, slides, code, diagram, video studio, 3D and more — that all share one memory. A single chat can write a document, design a deck, build and deploy a full-stack app, render a video or reconcile a pile of invoices, and hand the result to a surface you can edit.

Yes. The free plan includes 25,000 credits a month and needs no credit card. Paid plans start at about $16.67 per month billed yearly, with usage-based credits shared across every surface.

What if the tool I need is not in Xenition?

Ask for it in the product chat. The team reviews every request and most ship within 3 to 7 days.

How is Xenition different from a chatbot with plugins?

A chatbot returns text. Xenition returns work on a surface you can keep editing, and remembers it. It also does things a single-surface tool structurally cannot: learning paths with decaying mastery that can refuse to teach a topic whose foundation has lapsed, invoice reconciliation where confidence comes from arithmetic rather than a model's self-assessment, explainer videos where narration is measured before any frame is cut, and meeting notes that expand your own typed notes and drop any action item that cannot quote its source line.

Can Xenition build and deploy a real application?

Yes. Describe an app and Xenition generates a working product with a real Postgres database, authentication, storage, an API, a web front end and a native mobile app, then deploys it. There are also 153 full-stack templates, each with a live demo.

Which apps does Xenition connect to?

121 apps including Slack, Gmail, Google Calendar, Google Drive, Notion, GitHub, Linear, Jira, HubSpot, Salesforce, Stripe, QuickBooks and Airtable. Agents can act in them, with an approval gate on anything destructive.

Is Xenition available outside the browser?

Yes — a desktop app for macOS, Windows and Linux with a global hotkey and silent auto-updates, plus native mobile apps for iOS and Android. The interface is available in 36 languages.

All connectors

Greenhouse integration

Applicant tracking and recruiting software to optimize your entire recruiting process

Connect Greenhouse to Xenition and work with it from chat, from an agent, or on a schedule — alongside every other app you have connected, in one workspace.

What you can do with Greenhouse

Ask in plain language and Xenition calls the right one:

Reactivate Greenhouse user — Reactivate a previously deactivated Greenhouse user via the Harvest v3 API so they can sign in again. Use when you need to restore sign-in access for a user account that was previously deactivated, for example when an employee returns. Reactivation restores access only; job permissions that were removed during deactivation are not restored. The call is safe to repeat on an already-active user.
Anonymize Greenhouse candidate — Tool to anonymize selected categories of personally identifiable data on a Greenhouse candidate via the Harvest v3 API, for GDPR or right-to-be-forgotten requests. Use when you must permanently redact specific classes of a candidate's PII (such as full name, contact details, tags, attachments, or notes) while retaining the candidate record. WARNING: anonymization is irreversible — the selected fie
Apply Greenhouse candidate tag — Tool to apply an existing candidate tag to a candidate via the Greenhouse Harvest v3 API. Use when you want to label a candidate with a tag that already exists in the organization's candidate-tag dictionary. Both the candidate and the tag must already exist; the tag is not created by this action.
Bulk create Greenhouse blocked spam sources — Tool to add multiple blocked spam sources to Greenhouse in a single request via the Harvest v3 API. Use when you need to block several IP addresses, email addresses, CIDR ranges, and/or email domains at once so future applications from them are automatically rejected. The request is processed asynchronously: Greenhouse returns a bulk request uuid and a status URL to poll for completion.
Bulk create Greenhouse custom field options — Tool to add many custom field options at once to select-type custom fields via the Greenhouse Harvest v3 API. Use when you need to create multiple options across one or more single_select/multi_select custom fields in a single call. The request is processed asynchronously: Greenhouse returns a bulk request uuid and a status URL to poll for completion and the created option ids.
Bulk create Greenhouse openings — Tool to asynchronously create many Greenhouse openings across one or more jobs in a single Harvest v3 call. Use when you need to add headcount slots in bulk and want a single submission that Greenhouse processes in the background. Returns a bulk_action_uuid and status_url to poll for per-row results; openings are created independently, so some rows may succeed while others fail.
Bulk deactivate Greenhouse users — Tool to asynchronously deactivate many Greenhouse users in a single Harvest v3 call, up to the bulk-endpoint cap per request. Use when you need to revoke sign-in access for several users at once (for example when offboarding a group of employees) and want one submission that Greenhouse processes in the background. Deactivation only blocks sign-in: each user's record and history are preserved and a
Bulk delete Greenhouse custom field options — Tool to archive many custom field options at once by id via the Greenhouse Harvest v3 API. Use when you need to remove multiple options from one or more select-type custom fields in a single call. This is destructive: archived custom field options are removed from the field and can no longer be selected, so restoring them requires re-creating the options. The request is processed asynchronously: G
Bulk update Greenhouse blocked spam sources — Tool to asynchronously update the note on many Greenhouse blocked spam sources in a single Harvest v3 call. Use when you need to revise notes on multiple blocklist entries at once and want a single submission that Greenhouse processes in the background. Returns a bulk_action_uuid and status_url to poll for per-row results; only the note can be changed (source_type and value are immutable here), an
Bulk update Greenhouse custom field options — Tool to asynchronously edit many Greenhouse custom field options in a single Harvest v3 call. Use when you need to rename, reorder, or set external ids on several options at once and want a single submission that Greenhouse processes in the background. Returns a bulk_action_uuid and status_url to poll for per-row results; each option is updated independently, so some rows may succeed while others
Bulk update Greenhouse departments — Tool to asynchronously update many Greenhouse departments in a single call via the Harvest v3 API. Use when you need to rename or re-key several departments at once, each identified by its Greenhouse id, up to Greenhouse's bulk-endpoint cap per request. The request is processed asynchronously: Greenhouse validates and updates each department independently and returns a bulk request uuid plus a sta
Bulk update Greenhouse offices — Tool to asynchronously update many Greenhouse offices in a single Harvest v3 call. Use when you need to rename offices, set or clear their location or external_id, or reposition them in the office tree in bulk, and want a single submission that Greenhouse processes in the background. Returns a bulk_action_uuid and status_url to poll for per-row results; offices are updated independently, so some r
Bulk update Greenhouse openings — Tool to asynchronously update many Greenhouse openings in a single call via the Harvest v3 API. Use when you need to re-key, open, close, or update custom fields on several openings at once, each identified by its immutable Greenhouse id, up to Greenhouse's bulk-endpoint cap per request. The request is processed asynchronously: Greenhouse validates and updates each opening independently and return
Bulk update Greenhouse users — Tool to asynchronously update many Greenhouse users in a single call via the Harvest v3 API. Use when you need to change fields on several users at once (for example an HRIS sync updating job titles, offices, departments, or custom fields), each identified by its Greenhouse id, up to Greenhouse's bulk-endpoint cap per request. The request is processed asynchronously: Greenhouse validates and updat
Create Greenhouse application — Tool to create a new application for an existing Greenhouse candidate via the Harvest v3 API. Use when you need to attach a candidate to a job (supply candidate_id and job_id) or register a sourced candidate as a prospect (supply candidate_id and prospect: true). The two request shapes are mutually exclusive: a job application uses job_id while a prospect uses prospect: true with optional prospect
Create Greenhouse approval flow — Tool to create a multi-step approval flow on a Greenhouse job via the Harvest v3 API. Use when you need to gate a job opening or offer behind one or more tiers of approvers, supplying the job_id, approval_type, whether the tiers resolve sequentially, and the seeded approver_groups. The flow is created with approval_status=pending; offer_candidate flows additionally require the offer_id.
Create Greenhouse attachment — Tool to attach a file to an existing Greenhouse application via the Harvest v3 API. Use when you need to upload a document (resume, cover letter, offer letter, etc.) to a candidate's application, supplying the application_id, filename, type, and exactly one of content (base64-encoded bytes) or url (a publicly fetchable link). The returned download URL is time-limited and expires after seven days.
Create Greenhouse blocked spam source — Tool to add a new IP address, CIDR range, email address, or email domain to the organization's spam blocklist via the Greenhouse Harvest v3 API. Use when you need to block a sender or network source so that future applications and emails from it are automatically rejected. The source_type field controls how value is interpreted (single IP, IP range, single email address, or whole email domain).
Create Greenhouse candidate — Tool to create a new candidate profile in Greenhouse via the Harvest v3 API. Use when you need to add a candidate to your organization, optionally creating their first application (an applicant on a specific job, or a prospect) in the same call. Only first_name and last_name are required; all other profile and application fields are optional.
Create Greenhouse candidate education — Tool to add a new education entry to a Greenhouse candidate's profile via the Harvest v3 API. Use when you need to record a candidate's schooling, including the school, degree, and discipline (referenced by custom-field option ids) along with start and end dates. Only candidate_id is required; school, degree, and discipline are optional but must reference existing custom-field option ids.
Create Greenhouse candidate employment — Tool to add a new work-history (employment) entry to a Greenhouse candidate's profile via the Harvest v3 API. Use when you need to record a candidate's past or current role. The candidate id, company name, job title, and start date are required by Greenhouse; omit end_date to represent a current, ongoing position.
Create Greenhouse candidate tag — Tool to add a new tag to the organization's candidate-tag dictionary via the Greenhouse Harvest v3 API. Use when you need to register a reusable candidate tag (by name) so it can later be applied to candidates. Tag names are case-insensitive; if a matching tag already exists Greenhouse returns the existing tag rather than creating a duplicate.
Create Greenhouse custom field — Tool to add a new custom field to your organization's dictionary via the Greenhouse Harvest v3 API. Use when you need to define a new custom data point (text, number, currency, select, date, etc.) on jobs, candidates, applications, offers, openings, or other Greenhouse resources. field_type, value_type, and name are required; select-type fields (single_select/multi_select) require custom_field_opt
Create Greenhouse custom field department — Tool to restrict a custom field's visibility to one additional department via the Greenhouse Harvest v3 API. Use when you want a custom field to appear only on jobs, offers, or candidates that belong to specific departments and need to add another department to that allow-list. Each call adds a single department association; repeat the call to grant visibility to more departments.
Create Greenhouse custom field office — Tool to restrict a custom field's visibility to one additional office via the Greenhouse Harvest v3 API. Use when you need to make an existing job, opening, or offer custom field visible for one more office without replacing its existing office restrictions. Supply the target custom_field_id and the office_id; only one office can be added per call.
Create Greenhouse custom field option — Tool to add a new selectable value to a single_select or multi_select custom field via the Greenhouse Harvest v3 API. Use when you need to extend a custom field with an additional option (for example syncing option values from an external HRIS). Supply the target custom_field_id and the option name, plus an optional sort_order and external_id; the field must be of a select type for the option to a
Create Greenhouse department — Tool to create a new department for the organization via the Greenhouse Harvest v3 API. Use when you need to add a department with an optional external_id and an optional parent department (by id or external_id) to nest it in the department tree. The name is required and must be unique among active departments; parent_id and external_parent_id are mutually exclusive.
Create Greenhouse interview — Tool to create a scheduled interview against a candidate application in Greenhouse Harvest. Use when you need to place a candidate's interview onto the schedule with a start/end time, panel of interviewers, and the corresponding calendar event. The interview is created for a specific interview-plan slot (job_interview_id) and tied to an external calendar event id.
Create Greenhouse job — Tool to create a new Greenhouse job from an existing template via the Harvest v3 API. Use when you need to spin up a new requisition that inherits its interview plan, scorecards, hiring team, and approval workflow from a template job. template_job_id and number_of_openings are required; department/office can be set by Greenhouse id or by partner external_id (the two forms are mutually exclusive),
Create Greenhouse job hiring manager — Tool to assign a user as a hiring manager on a Greenhouse job via the Harvest v3 API. Use when you need to add an existing organization user to a job's hiring team in the hiring manager role. Both job_id and user_id are required and must reference resources that already exist in your organization; the call returns the assignment's row id, which is needed to later revoke it.

…and 20 more Greenhouse actions available in the workspace.

Give an agent access to Greenhouse

An agent you create can use Greenhouse on your behalf and keep working while you do something else. Every action an agent takes goes through an approval gate first, so nothing touches your Greenhouse account without you agreeing to it.

Other connectors

Frequently asked questions

How do I connect Greenhouse to Xenition?

Open the connectors directory in Xenition, find Greenhouse, and sign in when the authorisation window opens. The connection is managed for you — there is no API key to create, paste or rotate.

What can Xenition do with Greenhouse?

Xenition can run 50 different Greenhouse actions, including Reactivate Greenhouse user, Anonymize Greenhouse candidate, Apply Greenhouse candidate tag. You ask in plain language and the right one is called for you.

Can an agent use Greenhouse on my behalf?

Yes. Agents can use Greenhouse while you do something else, and every action passes through an approval gate before it runs.

Is there a free plan?

Yes. Xenition starts free with 25,000 credits a month and no credit card, and all connectors are available on every plan.