Appearance
Integrations
Integrations in Modulos are built around clear boundaries: project-level service access, user-level OAuth access, and API access for automation.
Choose the right integration
| You want to… | Use | Why |
|---|---|---|
| Power tests and continuous monitoring | Sources | Sources are project-level service accounts designed for reliable, shared automation |
| Let Scout search and retrieve external context | Scout connectors | Connectors are user-scoped and only see what the connected user can access |
| Access the Modulos API from code and tooling | API tokens | Tokens let scripts authenticate as a user without interactive login |
Rule of thumb
If it should keep working when people change teams, use a source. If it should only see what a specific person can see, use a connector. If it’s a script, use an API token.
The three integration primitives
| Primitive | What it connects | Where it’s managed | Scope |
|---|---|---|---|
| Sources | Service accounts and machine-to-machine integrations | Project → Settings → Sources | One project |
| Scout connectors | User accounts via OAuth | Settings → Connectors | One user |
| API tokens | User tokens for API access | Settings → API Tokens | One user |
Sources
Sources are project-level service accounts. They are attached to a project and are used to power Testing and other project-scoped automation.
Scout connectors
Connectors are user-level accounts connected to a specific user, usually via OAuth. They are used to bring user-scoped external context into Scout.
API tokens
API tokens are per-user bearer tokens used for programmatic access to the Modulos API.