Package Information
Available Nodes
Documentation generating…
Documentation
n8n-nodes-corem
This is an n8n community node for Corem, an HR and workforce management platform (attendance, leave requests, documents, and more).
n8n is a fair-code licensed workflow automation platform.
Installation
Operations
Credentials
Compatibility
Usage
Resources
Version history
Installation
Follow the installation guide in the n8n community nodes documentation.
This package provides two nodes:
- Corem — performs actions against Corem
- Corem Trigger — starts a workflow when a Corem event occurs
Operations
Corem (action node)
| Resource | Operation | Description |
|---|---|---|
| Send | Send a custom email | |
| Request | Change Status | Change the status of a request (leave, permit, ...) |
| Request | Get | Get an existing request by ID |
| User | Create | Create a new user (the password is generated by Corem and delivered via welcome email) |
| User | Get | Get an existing user by ID |
| Attendance | Export Summary | Export a period's attendance summary as an Excel file, one sheet per user or a single sheet for everyone |
| Document | Create | Create a document with an attachment, shared with chosen sites/teams/users |
| Document | Get | Get an existing document by ID |
Corem Trigger
A single trigger node with an Event Type dropdown covering every Corem event Corem currently exposes (requests, documents, attendance, badges, users). Selecting an event subscribes the workflow's webhook to it; deactivating the workflow unsubscribes.
Credentials
The node authenticates with a Corem API credential:
- Base URL — your Corem domain, e.g.
https://acme.corem.cloud(no trailing slash) - API Key — the key of a Corem service account
To create a service account and its API key, in Corem go to Settings > OAuth2.0 > Service Account. The key is shown only once, at creation time.
The service account acts as the Corem user it is linked to: it inherits that user's roles and permissions, which determine what the node can see and do (e.g. which sites/teams/users appear in the dynamic dropdowns, or whether user/document creation is allowed).
Compatibility
Tested against n8n 2.38.7.
Usage
- The Document > Create operation expects the attachment as binary data on the input item (e.g. from an HTTP Request or Read Binary File node upstream); set the "Input Binary Field" parameter to match.
- The Attendance > Export Summary operation returns the generated Excel file as binary data on the output item.
- Dropdown fields (sites, teams, users, roles) are scoped to what the linked service account's permissions allow; an empty list usually means the service account's user lacks visibility or the relevant permission.
Resources
Version history
See CHANGELOG.md.