Why Use Named Credentials?

ServiceNow

Salesforce ServiceNow Setup

Create Named Credentials

Integration Preparation in Salesforce

Jira

Release Notes

Installation Guide

Configuration Guide

Working with ‘Related Jira Issue’ component

Peeklogic Jira Connector feature configurations

Peeklogic Jira Connector feature configurations
Access Configuration
Salesforce Lookup field configuration
Configure mapping for manual creation of Jira Service Request
Configure mapping for manual creation of Jira Issue
Setup automatic update Jira Schema in Salesforce
Add and configure Jira Project and Jira Issue Type
Select Named Credentials for Jira Synchronization
Salesforce Notification
Add and configure Jira Issue Type fields
Move Jira Issue between Projects
Jira Assets
Email - to Case
Configure Team feature

Jira Admin Custom Settings

Comments Synchronization

Attachments Synchronization

Automation Process

Azure Devops

Configuration Guide

Guide to deploy an Azure Function

Azure Setup

Azure Devops Related Records Component

Azure Automation and Actions

Netsuite

Installation

Configuration Guide

Peeklogic NetSuite Connector feature configurations

General Configuration

User requirements

Object Synchronization

Salesforce Automation

Netsuite Component

Introduction

AI Capabilities Matrix

Authentication Setup

Feature Configuration (AI Configurator)

Creating & Managing AI Model Configurations

Making AI Requests and Viewing Responses

Custom Flow Integration with AI Request Action

Notes

Why Use Named Credentials?

Security: Credentials are stored securely in Salesforce, not in code.

Maintainability: Easily update credentials in one place without code changes.

Best Practice: Salesforce recommends Named Credentials for all external callouts.

From Setup to Success — All in One Place

Why Use Named Credentials?

Ready to simplify your Salesforce integrations?