Resource Templates
A Resource Template is a reusable blueprint built on top of an Identity Provider (IDP). It defines the OAuth scopes and, optionally, the default platform-level credentials that a specific service integration requires.
Think of a Resource Template as the definition of what a service connection needs — the actual live credentials and environment-specific settings are configured when you deploy a Managed Resource.
Location: Library > My Artifacts > Resource Templates
What You Can Do
| Action | Description |
|---|---|
| Create | Set up a new Resource Template via a multi-step wizard |
| Edit | Modify an existing template |
| View | Inspect template details in read-only mode |
| Delete | Permanently remove a template |
| Search | Filter templates by name |
Creating a Resource Template
Navigate to Library > My Artifacts > Resource Templates and click Create. The wizard walks you through up to four steps (the Platform Credentials step is conditional).
Step 1 — Basic Details
| Field | Required | Description |
|---|---|---|
| Name | Required | A unique name for this template, scoped to the selected IDP. Validated in real time as you type. |
| Identity Provider | Required | The IDP this template is built on. This field cannot be changed after creation. |
| Description | Optional | A markdown-supported description of what this template represents. |
| Activity Group | Optional | The group this resource activity will appear under in the activity palette. |
| Icon | Optional | Pick from the icon library or upload a custom SVG file. |
| Version | Optional | A version identifier for this template (e.g., 1.0.0). |
The Identity Provider field is locked once the template is saved. To change the provider, create a new template.
Step 2 — Scopes
Define the OAuth scopes this resource requires. Each scope represents a specific permission the platform will request from the provider.
Click Add Scope to add a row to the scopes table:
| Field | Required | Description |
|---|---|---|
| Scope ID | Required | The scope string as defined by the provider (e.g., https://www.googleapis.com/auth/spreadsheets). |
| Description | Optional | A human-readable explanation of what this scope grants. |
| Default | Optional | Mark this scope as selected by default when deploying a Managed Resource. Users can still deselect non-required scopes during deployment. |
You can add multiple scopes and reorder or remove them at any time before saving.
Step 3 — Platform Credentials (Conditional)
This step only appears when both of the following are true for the linked IDP:
- The IDP supports the Authorization Code grant type.
- The IDP has Allow Default Connection enabled.
When these conditions are met, you can configure shared OAuth credentials at the platform level. These credentials are pre-filled when deploying Managed Resources, reducing the need for users to enter them manually.
For each environment defined in the IDP, provide:
| Field | Required | Description |
|---|---|---|
| Environment | — | The IDP environment these credentials apply to (auto-populated from the IDP). |
| Grant Type | Required | Select Authorization Code or Client Credentials for this set of credentials. |
| OAuth Client ID | Required | The client ID issued by the provider for your registered application. |
| OAuth Client Secret | Required | The client secret issued by the provider. Stored securely. |
Step 4 — Review
Review all settings before saving. Click Back to make changes or Save to create the template.
Once saved, the Resource Template is available organization-wide and can be used to deploy Managed Resources.
Editing a Resource Template
- Navigate to Library > My Artifacts > Resource Templates.
- Locate the template you want to modify.
- Click the Edit (pencil) icon.
- Update the relevant fields — the linked IDP cannot be changed.
- Click Save to apply changes.
Deleting a Resource Template
- Navigate to Library > My Artifacts > Resource Templates.
- Click the Delete (trash) icon next to the template.
- Confirm the deletion in the dialog.
Deleting a Resource Template will affect any Managed Resources deployed from it. Verify no active deployments depend on this template before deleting.
What's Next
Once a Resource Template is ready, deploy it as a Managed Resource with environment-specific credentials and connection settings.