Integrations / Integration basics
Integrations overview
Understand how RIB Creative connects projects, services, and external tools.
Integrations overview
Integrations let RIB Creative connect your project to the services it needs to build, sync, publish, and operate real apps.
Some integrations control how the platform works. Others become part of the app you are building.
Integration types
RIB Creative uses a few different integration patterns:
- Connectors govern what platform tools and agents are allowed to use.
- GitHub sync connects a RIB project to a GitHub repository.
- Workspace integrations are shared settings managed by workspace owners and admins.
- Project integrations configure app-specific capabilities such as payments or auth.
These patterns are related, but they are not interchangeable.
For example, Stripe has a workspace connector policy and a project-level payment setup. GitHub sync is an integration, but it is not part of the connector catalog today.
What connectors control
Connectors are governance surfaces. They answer questions such as:
- Is this capability allowed in the workspace?
- Should the agent ask before using it?
- Is the setting inherited from the workspace or overridden for one project?
- Which sensitive operations are blocked?
Current connector policy modes are:
| Mode | Meaning |
|---|---|
| Allow | The capability can be used without asking each time. |
| Ask | The product should ask before using the capability. |
| Deny | The capability should not be used. |
What integrations can affect
Depending on the integration, it may affect:
- Project source code.
- Agent capabilities.
- Backend readiness.
- Payment setup.
- Authentication setup.
- Publish readiness.
- Workspace governance.
Before using an integration, confirm whether it is a workspace setting, a project setting, or both.
Good integration habits
- Keep secrets out of prompts and markdown.
- Use project settings for project-owned credentials.
- Use workspace settings for shared governance.
- Prefer
Askfor sensitive operations until your team has a clear policy. - Test auth and payment flows before publishing.
- Resolve GitHub sync warnings before releasing.
Copyable prompt
Review this project's integrations.
Tell me which services are connected, which ones are blocked by policy, and what needs setup before this app can be published safely.
Do not reveal or request secret values.
Next steps
- Learn connector policies: Connectors
- Sync code: GitHub sync
- Configure payments: Stripe