Integrations at a glance
ApptiveGrid can be connected to other systems in four ways.
| Way | Direction | Set up in |
|---|---|---|
| Integration steps in a Flow | ApptiveGrid → outside system | Flow editor |
| Webhooks | ApptiveGrid → outside system | Space settings |
| Webhook trigger | Outside system → ApptiveGrid | Flow editor |
| API | both directions | API credentials |
Which way for what
| Goal | Way |
|---|---|
| Send a message to Slack or Teams | Integration step |
| Create a contact in HubSpot | Integration step |
| Call any system | Integration step HTTP request |
| Notify another system of changes | Webhook |
| Start a Flow from outside | Webhook trigger |
| Your own application that reads and writes data | API |
Check first whether a Flow is enough
The API is powerful, but requires programming skills. For most connections, a Flow with the HTTP request step is enough — with no code of your own.
Credentials for integration steps
The ready-made integration steps differ in whether you need your own credentials.
Without your own credentials
| Service | You provide |
|---|---|
| OpenAI | Only the prompt and optional instructions |
OpenAI runs through ApptiveGrid
You don't need your own OpenAI contract or API key. The step is ready to use as soon as your plan includes it.
Check what data you're passing along, regardless
The content of a prompt leaves ApptiveGrid and is sent to an external service. Don't pass along personal or confidential data without a prior data protection review.
With your own credentials
For these services, you need your own account and enter the credentials in the respective Flow step:
| Service | You enter | Where to get it |
|---|---|---|
| Slack | Webhook URL | Slack admin, set up an incoming webhook |
| MS Teams | Webhook URL | Teams channel, set up a connector |
| Firebase Cloud Messaging | API key, device tokens or topic | Firebase console |
| HubSpot | API token | HubSpot account |
| Magenta Business (SMS, Verify) | API key and secret | Contract with the provider |
| DATEV Payroll | Access key and password | Your DATEV account |
Credentials live in the Flow
The keys you enter are part of the Flow's configuration. Anyone with the Manage role in the Space can open the Flow.
Put Flows with sensitive credentials in a Space with a deliberately small circle of members — and use keys with restricted permissions wherever possible.
Get credentials before you start building
The most common stumbling block: the Flow is fully built, but the Slack webhook or HubSpot token is still missing — and obtaining it can take days in some organizations.
Sort that out before you start building.
Usable without configuration
These steps need neither a contract nor a key:
QR Code, PDF to text, URL to PDF, Import CSV file, Speech to text, Document Analyzer, Calendar Event, Wait, JavaScript
Some of these are plan-restricted.
When no ready-made step fits
The HTTP request step calls arbitrary systems. You specify:
| Field | Content |
|---|---|
| URL | Target address |
| Method | GET, POST, … |
| Content type | Format of the data |
| Headers | Header fields, e.g. for authentication |
| Body | The data to send |
| Username / Password | For basic authentication |
The path to almost any service
Anything with an open interface can be connected this way — including automation platforms that in turn reach hundreds of other services.
The editor itself points this out: Nothing fitting found? with the option to submit a request.
Where data lives
File attachments
Uploaded files live in object storage in the Europe (Frankfurt) region. Uploads from public forms use a separate, unauthenticated path.
For data protection inquiries, contact support — this documentation doesn't replace a legal assessment.
Next
- Actions — all integration steps in detail
- Webhooks
- API credentials