API
Build around your operation.
Read records and invoke supported operations from your own applications, services, and internal tools.
Explore the API guideIntegrationsConnect the operation.
Connect the operation.
Keep ownership clear.
Bring records, emails, files, and events into context around the clients, projects, and assets they concern. Keep the source identifiable and ownership clear as information moves between systems.
Source systemOwns the originating record
Agreed interfaceIdentity · units · revisions · errors
Helix workflowUses the verified operational context
API · MCP · WEBHOOKSConnect your systems.
Connect your systems.
Bring your agents.
Three ways into the same operating model. Records keep their meaning. Actions keep their permissions and review requirements.
MCP
Give assistants real context.
Connect compatible AI clients to operational knowledge and permitted tools, with explicit boundaries on what they can do.
Explore the MCP guideWEBHOOKS
Keep the next system in step.
Use operational events to trigger downstream work, with deliberate handling for delivery, duplicates, and recovery.
Explore the webhook guideUnlimited integrations in every plan. Technical limits and usage allowances still apply.Visit Developer Docs
Common integration boundaries
Start where the work crosses systems.
These are integration patterns to evaluate. Specific connectors, directions, and implementation scope are confirmed with your team.
ERP & financial systems
Orders, suppliers, commercial identity, and completion events. Agree which system owns stock balances and financial posting.
Example: link a purchase order to receiving evidence.Laboratory & equipment systems
Samples, results, units, methods, and supporting evidence. Keep imported observations distinct from reviewed results.
Example: associate a measurement with its sample and source file.Engineering & project systems
Parts, drawings, approved details, revisions, and work identity. Establish when a changed reference becomes applicable.
Example: retain the drawing revision used for a work package.Email, files & business tools
Link correspondence and files to clients, projects, sites, and assets using explicit links or configured identity mappings. Retain source references, freshness, and access controls; route uncertain matches to review.
Example: open a site record to find its access email, equipment plan, and service history.From raw source to usable evidenceBring in the result.
Bring in the result.
Keep the original.
File imports, versioned mappings, APIs, and webhooks connect observations to the work they describe. Review uncertain matches before they become decision evidence.
Preserve the source.
Retain the original file, source-system or instrument identity, acquisition time when supplied, and file integrity reference. Keep acquisition time distinct from import time.
Make interpretation repeatable.
Record the parser and mapping versions, source fields, unit conversions, and destination record. Corrections retain their relationship to the original import.
Route ambiguity to review.
Unmatched samples, conflicting identifiers, unexpected units, and duplicate files create an exception to resolve. A successful transfer is not automatically an accepted result.
Keep the method with the result.
Connect the sample, method revision, calibration or reference material, calculation, and specification used for review. A result retains the context needed to interpret it.
A useful integration brief
Make the contract between systems explicit.
Reliable operations depend on knowing what an exchange means, who owns it, and what happens when it fails.
Discuss an integration- Identity
- Stable identifiers and matching rules for the same record.
- Meaning
- Field mappings, units, status meaning, and applicable revisions.
- Authority
- Which system may create, change, approve, or reverse the record.
- Delivery
- Expected timing, duplicate handling, and reconciliation.
- Failure
- Visible errors, responsible owners, and a recovery path.
- Evidence
- Source provenance and verification before consequential use.
Before the handoff goes live
Test more than a successful import.
- Send the same event twice and check the result.
- Introduce missing identity, unexpected units, or an outdated revision.
- Confirm which actions remain blocked when source evidence is unavailable.
- Reconcile the records on both sides of the exchange.
Unlimited integrations in every plan.
Your plan does not cap the number of integrations. Confirm implementation work, third-party requirements, and any external service charges for the connections you need.
Questions & answers
A few useful details.
Your next step
Put your operation on Helix.
Choose a template, shape your workspace, and try the work for yourself. The sandbox is free forever.