Service desks: ServiceNow, Zendesk and Jira
How to connect ServiceNow, Zendesk and Jira Cloud. People read with their own logins and, if an admin turns it on, make single-record changes after confirming them.
Status: Available. All three are built on each vendor's published API, and validated in your instance during onboarding. Menu names move between releases: if a step doesn't match what you see, look for the nearest equivalent.
| System | Reads | Changes (off unless an admin turns them on) |
|---|---|---|
| ServiceNow | Any table the person can read: incidents, tasks, problems, changes, requests, knowledge, users and so on | Create or update one record in a table the admin lists, such as incident. Comments and work notes are fields (comments, work_notes). No deletes. |
| Zendesk | Tickets (with comments), users, organizations, groups | Create a ticket, or update one: status, priority, assignee, tags, custom fields, a public reply (comment) or a private note (internal_note). No deletes. |
| Jira Cloud | Issues (with comments and change history) and projects | Create an issue, update its fields, or add a comment. No deletes, and no status changes yet (Jira moves status through workflow transitions). |
Each person signs in with their own login, so ServiceNow, Zendesk and Jira only show and allow what that person could see and do there anyway. SourceLace never uses a shared admin account.
The redirect URL for all three is:
https://mcp.sourcelace.ai/connect/callback
At a glance
| Connects through | Sign-in | Network | Status | First test question | |
|---|---|---|---|---|---|
| ServiceNow | ServiceNow Table API | Personal sign-in | Nothing to open | Available | "Show my 5 newest open incidents in servicenow:prod." |
| Zendesk | Zendesk Support API (Search and Tickets) | Personal sign-in | Nothing to open | Available | "Show 5 open urgent tickets in zendesk:support." |
| Jira Cloud | Jira Cloud platform REST API (version 3) | Personal sign-in | Nothing to open | Available | "Show my Jira issues that are not done." |
Add each source with the usual steps. The network answers are explained in What your network needs. If the first test question fails, the error message tells you what to fix: look it up under When something goes wrong below.
Where it is on, Searching everything also searches ServiceNow and Zendesk tickets and Jira issues, with each person's own access, together with your other systems. For Jira links to open, set the source's site option.
ServiceNow
ServiceNow lives at your own address (such as corvanta.service-now.com), so your ServiceNow admin registers SourceLace once in your instance, which gives a Client ID. That ID is not a secret. SourceLace registers as a public client that proves each sign-in with PKCE, so no client secret is created, sent or stored.
What your admin does in ServiceNow
Once per instance. About 10 minutes.
Who: a ServiceNow admin (the admin role, or oauth_admin).
Before you start, write down your instance's name: the part before .service-now.com in its address, such as corvanta. If people open ServiceNow at a custom address, find the real name in All → System Properties (instance_name).
- Open All (top left), type
Application Registry, and open System OAuth → Application Registry. - Click New, then Create an OAuth API endpoint for external clients.
- Fill in:
- Name:
SourceLace. - Redirect URL: the redirect URL above.
- Public Client: tick it. This means "no client secret"; ServiceNow then requires PKCE, which SourceLace always uses. If your release has no Public Client box, this connector cannot be used on it yet; tell support the release name.
- PKCE Required: tick it if the box is there.
- Leave Access Token Lifespan (30 minutes) and Refresh Token Lifespan (100 days) as they are. People connect again when the refresh token runs out.
- Name:
- Click Submit, open the new entry again, and copy the Client ID.
- Make sure people can read the data: their ServiceNow roles (for example
itilfor incidents) decide what SourceLace shows them (see What people need in ServiceNow below).
Check that it worked: after your SourceLace admin adds the source, one person clicks Connect, signs in to ServiceNow, and asks for their open incidents. In ServiceNow, System OAuth → Manage Tokens lists their token.
ServiceNow's own guide: ServiceNow documentation (search for "Create an endpoint for clients to access the instance" and "Public client").
Add the source (SourceLace admin)
Kind: ServiceNow (servicenow).
| Option | Type | Default | Example | What it is |
|---|---|---|---|---|
instance |
Text | (required) | corvanta |
The name before .service-now.com. The instance's address, or one copied from the browser, also works. |
client_id |
Text | (required) | 3f2a... |
The Client ID from the Application Registry. |
To allow changes, turn on Allow changes and list the tables, such as incident, change_request.
What people need in ServiceNow
- Read access to the tables they ask about (for example the
itilrole for incidents). ServiceNow's ACLs decide everything. - Listing fields uses the data dictionary (
sys_db_object,sys_dictionary,sys_choice). If someone cannot read those, SourceLace falls back to the fields of one record they can see.
Queries
query (language servicenow_query) takes one JSON object with table, query, fields, display_value and limit:
{"table": "incident", "query": "active=true^priority=1^ORDERBYDESCopened_at",
"fields": ["number", "short_description", "state", "assigned_to"], "limit": 50}
query is ServiceNow's own encoded query, the same text a list's filter gives with Copy query. SourceLace refuses tables that hold the instance's own credentials (such as oauth_credential, or anything ending in _credentials), and refuses javascript: in queries, because it would run script on the instance.
Zendesk
Zendesk also lives at your own address (such as corvanta.zendesk.com), so your Zendesk admin creates an OAuth client for SourceLace. It is a public client: no secret, PKCE on every sign-in.
What your admin does in Zendesk
Once per Zendesk account. About 5 minutes.
Who: a Zendesk admin (Admin role in Zendesk Support).
Before you start, write down your subdomain: the part before .zendesk.com, such as corvanta, from Admin Center → Account → Brand management → Brands. Your help centre's own address (such as help.corvanta.com) does not work for sign-in.
- Open Admin Center (the four-squares menu → Admin Center).
- Go to Apps and integrations → APIs → OAuth Clients (on some accounts: Zendesk API → OAuth Clients) and click Add OAuth client.
- Fill in:
- Name:
SourceLace. Description: "Read and update tickets as the signed-in person". - Client kind: Public.
- Redirect URLs: the redirect URL above.
- Identifier: keep the suggested one or type
sourcelace. Copy it.
- Name:
- Click Save. If Zendesk shows a secret anyway, you don't need it; don't paste it anywhere.
Check that it worked: after your SourceLace admin adds the source, one person clicks Connect, signs in to Zendesk, and asks for their open tickets.
Zendesk's own guide: Zendesk help (search for "Using OAuth authentication with your application").
Add the source (SourceLace admin)
Kind: Zendesk (zendesk).
| Option | Type | Default | Example | What it is |
|---|---|---|---|---|
subdomain |
Text | (required) | corvanta |
The name before .zendesk.com. The address, or one copied from the browser, also works. |
client_id |
Text | (required) | sourcelace |
The OAuth client's Identifier. |
Sign-in asks for the scope read, plus tickets:write when an admin has made tickets writable. After turning changes on or off, people connect Zendesk again so their sign-in matches.
Queries and changes
query(languagezendesk_search) takes Zendesk's own search text, such astype:ticket status:open priority:urgent order_by:created sort:desc. Start withtype:ticket,type:userortype:organizationso every row has the same columns. One line, at most 1,000 characters. Zendesk returns at most 1,000 results per search, and new tickets can take a minute to appear in search.get_recordon a ticket can add itscomments.- With
ticketswritable, changes can setsubject,status,priority,type,assignee_id,group_id,requester_id,organization_id,tags,due_at,external_idandcustom_field_<id>, and add either a public reply (comment) or a private note (internal_note). Updates use Zendesk's "safe update", so they are refused if someone else changed the ticket since the preview.
Jira Cloud
Jira Cloud sign-in goes through Atlassian's central login, so SourceLace has one Atlassian app. After someone signs in, SourceLace asks Atlassian which Jira sites their sign-in reaches and uses the one named in the source's site option. Your Jira admin has nothing to register, unless your Atlassian organization restricts which apps people may approve.
What your admin does in Atlassian
Nothing is registered: SourceLace provides the Atlassian app. About 5 minutes, only if your organization restricts apps.
Who: an Atlassian organization admin (for app rules) and a Jira site admin (for product access).
- Write down your site: its
.atlassian.netaddress, from Atlassian Administration → Apps → Sites, such ascorvanta.atlassian.net, even if people open Jira at a custom domain. - Allow SourceLace if your organization blocks outside apps. In Atlassian Administration → Security → External apps (app access rules), allow SourceLace for the site.
- Product access: people need Jira access on that site (Atlassian Administration → Directory → Users → the person → Product access).
- People connect and, on Atlassian's consent page, choose the Jira site under Use app on.
Check that it worked: one person connects and asks for their open issues.
Atlassian's own guide: Atlassian Support (search for "Manage app access rules").
Permissions SourceLace asks for: read:jira-work (read projects and issues), read:jira-user (read people's names) and offline_access (stay connected), plus write:jira-work (create and edit issues and comments) only on sources where an admin made issue writable.
Names of Jira people in saved chats
SourceLace does not keep a person's Atlassian account ID with their sign-in. When an answer from Jira that names people is saved in a chat, the names stay in that chat until the chat is deleted or reaches your organization's retention period. Atlassian asks every app to report the people it keeps this way, so SourceLace does: when Atlassian says an account is closed, that person's name is replaced in your saved chats with "a former Jira user", and when a name changes it is updated.
Add the source (SourceLace admin)
Kind: Jira Cloud (jira).
| Option | Type | Default | Example | What it is |
|---|---|---|---|---|
site |
Text | (none) | corvanta.atlassian.net |
Recommended: the Jira site (step 1). Needed if people reach several sites, and for links to issues in Searching everything. A bare name such as corvanta means corvanta.atlassian.net; an address copied from the browser also works. |
To allow changes, turn on Allow changes with the object issue. After turning changes on or off, people connect Jira again.
Each person clicks Connect, signs in with their Atlassian account, and approves the site on Atlassian's consent page.
Queries and changes
query(languagejql) takes plain JQL, such asproject = CORV AND statusCategory != Done ORDER BY updated DESC, or JSON to choose the columns:{"jql": "project = CORV", "fields": ["summary", "status", "customfield_10010"]}. Jira needs at least one condition beforeORDER BY.get_recordon an issue can addcommentsandchangelog.- With
issuewritable: create an issue, update its fields, or add a comment. Descriptions and comments are sent as Jira's rich text, built from plain lines. Status changes and deletes are not offered.
When something goes wrong
ServiceNow
| What you see | What it means | What to do |
|---|---|---|
| "ServiceNow sign-in failed: ServiceNow refused SourceLace's app (...). Usually the app is not a public client ..." | The Application Registry entry has Public Client unticked, or the redirect URL differs. | Tick Public Client and check the redirect URL (step 3). |
| "ServiceNow sign-in failed: ..." (another reason) | ServiceNow's own reason follows. | Check steps 3 and 4. |
| "The ServiceNow instance for ... must be your instance's own name ... A custom address such as ... does not work for sign-in ..." | instance is a custom domain. |
Copy instance_name from System Properties. |
| "... needs the instance option: the name before .service-now.com, such as corvanta." | instance is empty. |
Fill it in. |
| "... needs the client_id option: the Client ID of the OAuth app registered in the instance's Application Registry" | client_id is empty. |
Copy it (step 4). |
| "ServiceNow: you do not have access to this (...). Ask your ServiceNow admin." | An ACL refused it. | Give the person a role that may read it (step 5). |
| "ServiceNow: that table or record does not exist, or you cannot see it." | The name is wrong, or the person's roles do not allow it. | Check the name and the roles. |
| "... holds credentials and is not available through SourceLace" | That table is never readable through SourceLace. | Query another table. |
| "javascript: runs script on the instance and is not allowed in a query" | The encoded query has javascript:. |
Remove it. |
| "SourceLace does not delete ServiceNow records. Change its state instead." | Deletes are not offered. | Update the state. |
| "Your ServiceNow session has expired." | The refresh token ran out (100 days by default). | Connect again. |
| "The ServiceNow client_id for ... has characters a Client ID never has." | The Client ID in the source has spaces or other stray characters, usually from copying. | Copy the Client ID again from the Application Registry entry, with nothing around it. |
| "ServiceNow: no ... record ... that you can see." | No record has that number or id, or your ServiceNow roles do not let you see it. | Check the number, and your roles. |
| "ServiceNow sent back data in an unexpected shape.", "ServiceNow answered with a web page instead of data (HTTP ...)." or "SourceLace refused to call an unexpected ServiceNow address." | The instance is under maintenance, asked for another sign-in, or sent SourceLace somewhere outside it. | Try again shortly. If it repeats, check the instance is up and contact support. |
Zendesk
| What you see | What it means | What to do |
|---|---|---|
| "Zendesk sign-in failed: ... In Zendesk, open Admin Center, Apps and integrations, APIs, OAuth Clients, SourceLace. Client kind must be Public ..." | The OAuth client is Confidential, or the Identifier differs. | Fix the client kind and Identifier (step 3). |
| "Zendesk sign-in failed: ..." (another reason) | Zendesk's own reason follows. | Check the redirect URL (step 3). |
| "... looks like your help centre's own address. Zendesk's API and sign-in only work at your <name>.zendesk.com address ..." | subdomain is a host-mapped address. |
Copy the subdomain from Brands (see Before you start). |
| "... needs the subdomain option: the name before .zendesk.com, such as corvanta." | subdomain is empty. |
Fill it in. |
| "... needs the client_id option: the Identifier of the OAuth client created in Zendesk's Admin Center" | client_id is empty. |
Copy the Identifier (step 3). |
| "Zendesk: you do not have access to this (...). Ask your Zendesk admin." | The person's Zendesk role does not allow it. | Ask a Zendesk admin. |
| "SourceLace cannot set '...' on a ticket. Use ..." | Only the ticket fields listed above can be changed. | Use those fields. |
| "Add either a comment or an internal_note in one change, not both." | Both were in one change. | Split it into two changes. |
| "Zendesk is limiting how fast SourceLace can call it. Wait a few seconds and try again." | Zendesk's rate limit. | Wait and ask again. |
| "The Zendesk subdomain for ... must be a name such as corvanta or a host such as corvanta.zendesk.com." | The subdomain option holds something else, such as a full web address with a path. | Enter only the name before .zendesk.com. |
| "The Zendesk client_id for ... has characters an identifier never has." | The OAuth client's Identifier has stray characters, usually from copying. | Copy the Identifier again from Admin Center, with nothing around it. |
| "Zendesk: no ... record ... that you can see." or "Zendesk: that record does not exist, or you cannot see it." | No record has that id, or your Zendesk role does not let you see it. | Check the id, and your role. |
| "Zendesk sent back data in an unexpected shape.", "Zendesk answered with a web page instead of data (HTTP ...)." or "SourceLace refused to call an unexpected Zendesk address." | Zendesk had a problem, or sent SourceLace somewhere outside your Zendesk address. | Try again shortly. If it repeats, contact support. |
Jira
| What you see | What it means | What to do |
|---|---|---|
| "Your Atlassian account did not give SourceLace access to any site. Connect again and, on Atlassian's consent page, choose your Jira site under 'Use app on' ..." | No site was chosen, the person has no Jira access, or the organization blocks outside apps. | Connect again and choose the site; otherwise steps 2 and 3. |
| "Your sign-in reached ..., but none of them gave Jira access ..." | The chosen site has no Jira (for example Confluence only), or the person has no Jira access there. | Choose the Jira site, or give Jira access (step 3). |
| "Your account reaches several Jira sites (...). An admin sets the site option on ... to choose one." | site is empty and the person reaches several sites. |
Set site (step 1). |
| "Your Atlassian account did not give SourceLace access to .... Connect again and choose that site on Atlassian's consent page." | The person approved another site than site. |
Connect again and pick the right one. |
| "... is not your Jira Cloud site's own address ..." | site is a custom domain. |
Use the .atlassian.net address (step 1). |
| "The Jira site for ... must be a Jira Cloud address such as corvanta.atlassian.net." | site is malformed. |
Fix it (step 1). |
| "the JQL needs a condition before ORDER BY, such as project = CORV" | The JQL has only an ordering. | Add a condition. |
| "Status changes go through a workflow transition, which SourceLace does not offer yet." | Status changes are not offered. | Change status in Jira itself. |
| "The jira connector is not available yet." | SourceLace's Atlassian app is not ready yet. | Contact support. |
| "Jira: that issue or project does not exist, or you cannot see it." | The key is wrong, or your Jira permissions do not let you see it. | Check the key, and your project permissions. |
| "Jira answered with a web page instead of data." or "SourceLace refused to call an unexpected Jira address." | Atlassian had a problem, or sent SourceLace somewhere outside your Jira site. | Try again shortly. If it repeats, contact support. |