Integrations
A process is useful when it talks to what you already run.
KulturPro doesn’t try to replace your systems. It exposes an API for whatever you want to automate, takes data from outside through a narrowly scoped token, and calls your services from the form itself.
- Suppliers
- Customers
- Contractors
- Emailed tasks with a verification code
- Webhook /v1/webhook/submit
- REST API /v1
- Public token forms
- Call to your HTTP service
- Email over SMTP or SendGrid
- Export to Excel and PDF
- Your own SQL Server
- Catalog table schema
- Read-only views
- Your own microservice
- Hosted under another suite
- Your ERP, over the API
Point by point
How each piece connects.
REST API
- One API under /v1
Everything the screen does goes through the same API: processes, tasks, modules, data, calendars, deadlines, users and assets.
- Uniform response
Every call returns success, data and a trace id you can use to find the error in the server log.
- Documented with Swagger
The documentation is generated from the code, so it never falls behind the installed version.
- Cookie session or token
The application uses session cookies; integrations get tokens scoped to what they are allowed to do.
Inbound webhook
- A token for one specific task
The token is generated from the application and is bound to one instance, one task and one field, with an expiry.
- Encrypted and stateless
It is encrypted with AES-256-GCM; tamper with it and it stops working. The server doesn’t need to store it.
- Written once
First write wins; a second one gets a conflict. A retry from the external system can’t duplicate the value.
- Rate limited
The entry point is public but rate limited, and answers with clear codes for expired, revoked or not found.
Outbound calls
- From the form
When the form opens, a field changes or a button is pressed, it calls your service and maps the response onto the fields.
- With the user’s session
The call can carry the session of whoever is working, so your service applies its own permissions.
- For outsiders too
A third party filling a form by email can trigger the same call, with an integrated authentication.
- Configured, not coded
The service, the headers and the mapping are defined in the designer.
Email and notifications
- SendGrid or your SMTP
The provider is chosen in the server configuration; there is also a local folder for testing.
- In each person’s language
Email goes out in the language stored for the recipient.
- A template per alert
Each deadline alert carries its own message.
- Links for outsiders
The email to an external user carries the task link and, separately, the verification code.
Extend with your own
- Companion microservice
A service of yours can share the same database and the same session, and return its result to the process through the webhook.
- Catalog tables
Dropdowns read tables in the product’s data schema, which can be filled over the API.
- Hosted in another suite
KulturPro runs as a child application of an ERP, taking its session and its permission map, switched on per company.
- No packaged connectors
There is no ready-made connector for SAP, Oracle or Dynamics: integration is done through API and webhook.
# 1. La aplicación emite un token para un campo de una tarea POST /v1/webhook/generate-token { "processInstanceId": 4821, "taskInstanceId": 9137, "componentId": "resultadoInspeccion", "expiresInHours": 48 } # 2. El sistema externo escribe una sola vez, sin sesión POST /v1/webhook/submit { "token": "eyJhbGciOi…", "value": "Conforme" } # 3. Respuesta 200 { "success": true, "traceId": "0HN7…" } 409 // ya se había escrito: el reintento no duplica 410 // el token venció o fue revocado
Rules
How we integrate.
Four decisions that avoid the kind of integration nobody dares touch later.
A token is not a master key
Each webhook token is good for one instance, one task and one field. It opens nothing else, and it expires.
Integration doesn’t guess
If a value arrives twice, the second attempt gets an explicit conflict instead of silently duplicating.
Nothing mandatory in the cloud
Email, AI and external services are optional: without them the product works, with less automation.
Data stays queryable
Everything lands in your own SQL Server tables; there is no proprietary format to rescue it from.
Questions
About integrating.
Can one of our systems start a process?
Yes, through the API. Starting a process is a call like any other, and it can also be triggered from a module record or from an asset element.
What if the external system can’t authenticate?
That is what the webhook is for: you generate the token from the application, hand it to the external system, and it can only write into the field it was issued for.
Are there outbound webhooks?
Not in the sense of subscribing to events. What exists are outbound calls configured in the form and in the task events.
Does it integrate with the corporate directory?
Not today. There is no single sign-on, SAML or Active Directory: users live in KulturPro, with its password policy and its second factor.
Bring the system it has to talk to.
In the demo we look at your actual case and tell you whether it is solved with the API, the webhook or a separate service.