Skip to main content

Salesforce Integration Guide

A clear guide to setup, customer details, testing and safe follow-up.

Friendly AzentiKo assistant waving hello
Salesforce logo

CRM objects and sales operations

How Can Salesforce Work With AzentiKo?

A Salesforce flow can create or update a CRM record from an enquiry, subject to confirmed AzentiKo support, Salesforce permissions and a reviewed object mapping.

Salesforce can hold leads, contacts, accounts, cases and opportunities. Start with the one object your team owns, map only the useful enquiry fields and agree how an existing record will be found before creating new data.

Check the connection before you start

This guide explains provider-side setup and a possible business workflow. It does not confirm an active AzentiKo connector, API endpoint, event, plan feature or vendor partnership. Ask our team to confirm the available route before buying another tool or connecting real customer data.

Confirm your setup with our team

Start With a Useful Job

These are planning examples, not reports of a live connection or customer results.

  • Create a lead for a new sales enquiry.
  • Create or update a case for support work.
  • Add a follow-up task for an assigned owner.
  • Link a contact to an account after human review.

Keep These Details Ready

  • A Salesforce organisation and an administrator-approved integration user or app.
  • A chosen object, required fields, record ownership and duplicate rule.
  • OAuth scopes and profile or permission-set access reviewed by the administrator.
  • AzentiKo confirmation of the supported event, action and plan access.

Ask your account owner to approve access. Never share passwords, tokens or real customer records through a public form or email.

Technical Words, in Simple English
API
A way for two systems to request or send information.
Webhook
A message sent to another system when an agreed event happens.
OAuth and scopes
A way to allow account access without sharing your password. Scopes describe which actions the connection is allowed to do.
Idempotency
A duplicate-safety rule: receiving the same event twice should not create the same lead or action twice.

Setup, one step at a time

Set Up and Test the Connection

Complete the provider steps using the official links below. Use only the AzentiKo connection method confirmed for your account.

  1. Choose the Salesforce object

    Select Lead, Contact, Case, Account or Opportunity based on the team process. Do not create multiple records for one enquiry without a clear reason.

  2. Review fields and validation

    Document required fields, record types, picklists, validation rules and owner assignment before building the mapping.

  3. Set up secure authorisation

    Salesforce uses connected-app or OAuth patterns. Ask the administrator to approve a least-privilege scope and keep client secrets outside the web root.

  4. Design duplicate and retry rules

    Choose an external reference or reviewed matching method, store returned record IDs safely and make retries idempotent where possible. Keep the Salesforce API version and organisation limits in the technical handover.

  5. Confirm AzentiKo support

    Ask the AzentiKo team which trigger and Salesforce action are available. The logo and example do not prove an active native integration.

  6. Test record ownership

    Use a sandbox or clearly marked test records where your organisation provides one. Check the selected REST API version, validation errors, owner, audit fields, limits and downstream notifications.

Send the Right Details to the Right Fields

Field mapping means deciding where each detail belongs. The names below are suggested business fields, not a published AzentiKo API format.

Suggested mapping for Salesforce — adjust it to your approved setup.
Detail from the enquiryWhere it could goWhat to check
Enquiry referenceExternal ID or custom fieldUse a stable value to recognise retries and updates.
Customer contact detailsLead or Contact fieldsValidate field security, country code and consent requirements.
Enquiry summaryDescription or Case commentUse a concise approved summary instead of unnecessary raw history.
Owner and urgencyOwner and priorityMap only valid users and picklist values in the target organisation.

Check These Before Going Live

  • Is the object and selected REST API version right for the team workflow?
  • Are validation rules, record types and organisation limits included in the test?
  • Can a retry find the same record through an external reference or approved matching rule?
  • Are permissions, logs and audit ownership clear?

Start with clearly labelled dummy data. Agree who will check failures, remove duplicate records and review access when a team member leaves. Switch on the live route only after the account owner approves the results.

If Something Does Not Work

Salesforce reports a field error

Check object, record type, required fields, field-level security and picklist values in the target organisation.

A duplicate record is created

Use a stable external reference or approved matching rule and save the returned record ID for future updates.

The token is rejected

Ask the Salesforce administrator to review connected-app settings, user permissions, OAuth scope, API version and environment. Never send a token in chat.

The record owner changes

Review assignment rules and automation in Salesforce; they may override the incoming owner value.

Need help? Share the tool name, a safe reference and the error message with our team. Remove secrets and customer details first.

Find help for your connection

Questions About Salesforce

Can we send enquiries to Cases instead of Leads?

That may fit a support workflow, but choose the object with your team and confirm the AzentiKo action that is available.

Should we test in a Salesforce sandbox?

If your organisation has a sandbox, it is a sensible place to validate mappings before live records are used.

Will Salesforce automatically prevent duplicates?

Duplicate rules depend on your organisation configuration. Still design an explicit matching and retry rule.

Is Salesforce a confirmed AzentiKo partner?

No partnership is implied. Ask for current availability and account-specific setup confirmation.

Official Setup References

Provider controls, permissions and charges can change. Use these official references alongside the setup confirmed by AzentiKo. Brand names and logos identify the tools; they do not imply an endorsement.

Build a complete route

Combine a destination with an approved automation or API route. Confirm each part before using live data.

Have a Connection in Mind?

Tell us your tool and the job you want it to do. We will help you check the route and the next step.

Your next step

Bring Your Questions.
See What Could Work for Your Business.

Explore the examples or request a guided walkthrough. Our team can help you check the plan, setup and tools you need.

A demo request opens your email app. Your team and ours will agree the next steps.