> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-agentix/configure-cortex-agentix/cases-and-issues-configuration/issue-syncing/create-a-sync-profile.md).

# Create a sync profile

Sync profiles provide a blueprint for how information is exchanged between Cortex AgentiX issues and external applications, by defining field mapping. This ensures that relevant data, such as **Status** or **Description**, is accurately transferred and maintains consistency, even if the systems use different terminology.

When you link an issue with an external application (such as Jira), or set up an automation, you can select the sync profile you want to use. Cortex AgentiX provides default outbound and inbound sync profiles, or you can create custom sync profiles as described in the following procedure.

How to create a sync profile

1. Go to **Settings** → **Configurations** → **Object Setup** → **Issues** → **Sync Profiles**.
2. Click **New Profile**.
3. Type a profile name and description.
4. Under **Integration**, select the external application with which you want to map fields, such as Jira V3 or ServiceNow V2.
5. Under **Sync Direction**, select **Inbound** or **Outbound**.

   If you select **Inbound**, you will define field mapping from the external application to Cortex AgentiX. If you select **Outbound**, you will define field mapping from Cortex AgentiX to the external application.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><p>If an issue is using bi-directional syncing, you need to provide both an Inbound and an outbound sync profile.</p></div>
6. Under **Field Mapping**, select a field to map and select the corresponding field. For example, Jira: Priority, Cortex: Severity.
7. Define one or more values for each field that you want to map.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><ul><li>Blank fields are skipped.</li><li>You must define exact values.</li><li>Custom status values are not currently supported.</li><li>Support is currently limited to a specific set of fields.</li></ul></div>
8. Click **Save**.

   Example

   In this example, the sync profile specifies Inbound mapping from Jira v3 fields to Cortex fields.

   ![Sync\_profile\_example.png](/files/CcejTOScg94v18JbmlRa)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-agentix/configure-cortex-agentix/cases-and-issues-configuration/issue-syncing/create-a-sync-profile.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.