Reference · Credentials
Connect Freshservice to BusyBot
Used by 1 BusyBot node.
Type
freshserviceApi 2 fields Fields
| Field | Type | Required | Notes |
|---|---|---|---|
API KeyapiKey | password | Yes | Freshservice API key. |
Domaindomain | string | Yes | Your Freshservice domain (e.g., mycompany.freshservice.com). |
Setting up Freshservice API
- In Freshservice API, create the credential this connection needs — the values listed in the table above. These are issued from your own Freshservice API account, usually under its developer, API or integrations settings.
- In BusyBot, open Credentials → Add credential and choose Freshservice API.
- Paste each value into the matching field and save.
- Add the Freshservice node to a workflow, select this credential, and run a simple operation to confirm it authenticates.
Security
- Secret values are encrypted at rest with AES-256-GCM, never written to logs, and readable only by your own account (to edit them).
- Grant the minimum scopes or permissions the operations you actually use require.
- Rotate the credential periodically, and immediately if it may have been exposed.
- Credentials are scoped to your account — a workflow cannot use another account's.
Frequently asked questions
Which BusyBot nodes use Freshservice credentials?
One node: Freshservice. Create the credential once and select it in that node.
What does a Freshservice credential need?
2 fields: API Key, Domain. Required: API Key, Domain. The values come from your own Freshservice account.
How are Freshservice secrets stored?
Secret values are encrypted at rest with AES-256-GCM, never written to logs, and scoped to your account: only you can open the credential again to edit it, and a workflow in another account cannot use it.
Nodes that use Freshservice API
One credential works across every node below — create it once and reuse it.