# Pascal Integrations

Source: https://www.trypascal.io/platform/integrations

Your systems. Ready for connected work.

Bring records, events, and supported actions from your existing tools into Pascal. See what each connection can do and who can use it.

## Capabilities

### Find the connection

Explore the connector catalog and the records, queries, and actions each integration supports.

### Connect an account

Set up an account with the access the work needs. Keep credentials private and connection scope explicit.

### Bring in business data

Connect source records with Pascal’s business model. Retain source identity and the context needed to understand a value.

### Make actions available

Give authorized people, workflows, and agents access to supported actions through the same connection.

### Review connection health

Inspect account status and capability availability. Resolve missing access or configuration before relying on the connection.

### Control the access

Apply current account, workspace, and source permissions when the work happens. Keep the resulting action and its outcome inspectable.

## Connected context

Use connected records in Ontology and Data Infrastructure. Give Agents, Workflows, Forge functions, and internal applications access to the same supported tools.

- Business applications, databases, warehouses, files, APIs, and event sources
- The records, data feeds, incoming events, and approved actions each connection supports
- Connected accounts, permissions, delivery history, health, changes, and recovery

## Controls and permissions

Credentials stay private, and permissions are checked whenever a connection is used. Changes to an external system remain unconfirmed until that system reports what happened. A retry alone cannot establish success.

## Example

An engineering team needs repository context to investigate a change. The GitHub connection supplies repository metadata and pull-request history to the workspace. The team can inspect the connected account and its available reads before deciding whether a later workflow also needs permission to write.

## Workflow

### Inspect the available capabilities

- Review repository metadata and pull-request history. Assess the specific operations you need before connecting an account.

### Check the connected account

- Inspect the Meridian account, its connection status, and the read operations available to the workspace.

### Match permission to the operation

- Repository reads are available in this example. A repository change needs its own write capability and authorization; connecting the account does not grant them.

## Next steps

Start with one workflow and the reads, events, or actions it needs. Confirm account access and the supported operations before expanding.

- [Contact sales](https://www.trypascal.io/contact)
- [Software Factory](https://www.trypascal.io/solutions/software-factory)