Close Menu
SalesforceCodex
    Facebook X (Twitter) Instagram
    Trending
    • How to Build a Generic Modal Window in Lightning Web Component
    • Top 10 Salesforce Flow Features of Salesforce Summer ’25
    • Unlock the Power of Vibe Coding in Salesforce
    • How to Implement Dynamic Queueable Chaining in Salesforce Apex
    • How to Implement Basic Queueable Chaining in Salesforce Apex
    • How to Suppress PMD Warnings in Salesforce Apex
    • Top 10 PMD Issues Salesforce Developers Should Focus on in Apex
    • How to Use Graph API for Outlook-Salesforce Connection
    Facebook X (Twitter) Instagram
    SalesforceCodex
    Subscribe
    Thursday, May 29
    • Home
    • Architecture
    • Salesforce
      • News
      • Apex
      • Integration
      • Books Testimonial
    • Questions
    • Certification
      • How to Prepare for Salesforce Integration Architect Exam
      • Certification Coupons
    • Integration Posts
    • Downloads
    • About Us
      • Privacy Policy
    SalesforceCodex
    Home»Salesforce»Apex»Verify Phone using Flow HTTP Callout

    Verify Phone using Flow HTTP Callout

    Dhanik Lal SahniBy Dhanik Lal SahniFebruary 28, 2023Updated:January 15, 20251 Comment5 Mins Read
    Facebook Twitter Pinterest LinkedIn Tumblr Email
    Verify Phone Using VeriPhone API - SalesforceCodex
    Share
    Facebook Twitter LinkedIn Pinterest Email

    Businesses need verified customers/users so that they can share important information about business/ regulatory updates. Businesses will need a verified phone number in every stage of the customer lifecycle including account creation, transaction authentication, and ongoing customer engagement activities to decrease the potential for compromised security. Phone/Mobile verification can be done using many ways. This post will verify phone using Flow Http Callout (Beta) with VeriPhone API.

    We have already published a post to Verify Phone in Salesforce using VeriPhone API using a low code approach. This post is using the same API to verify phones using no-code approach.

    HTTP Callout (Beta) is a new feature in the Salesforce Flow to call external API without code. This way we can easily maintain external API interaction. Right now it is supporting only GET operation of API.

    Steps for implementing and integrating VeriPhone API

    1. Setup User in VeriPhone API
    2. Create a Permission Set for Callout
    3. Create an External Credential and a Named Credential
    4. Create Salesforce Flow to Verify Phone/Mobile
    5. Test Flow

    Let us implement all these steps one by one

    1. Setup User in VeriPhone API

    Create a free user in VeriPhone system. You can use your Gmail or GitHub user also for creating a free user account.

    VeriPhone Free Registration | SalesforceCodex

    Once registration is done, verify the account using the confirmation link. A confirmation email will be sent to the email which is used for registration. After confirmation, you can see your API key detail in the setting section.

    VeriPhone API Setting | SalesforceCodex

    2. Create a Permission Set for Callout

    Create a permission set Callout User PS and assign this permission set to yourself. This permission set will be assigned to all users who need to call external API using flow. You can create a permission set from Setup -> Permission Sets

    Callout Permission Set | SalesforceCodex

    Assign object permission (CRUD) “User External Credentials” to store encrypted tokens used by named credentials.

    User External Credentials ! SalesforceCodex

    3. Create an External Credential and a Named Credential

    We will create a named credential to call external API. We have a lot of benefits using named credentials, you can check our video for more information. We will create external credentials first before creating named credentials.

    An external credential represents the details of how Salesforce authenticates to an external system via an authentication protocol. In our case, we have an API key that is passed in the URL to authenticate callout so we will use a custom authentication protocol.

    Once we set the authentication protocol, set permission set mapping which will indicate who all users can call named credentials.

    Callout Permisson Set Mapping - SalesforceCodex

    We are done with the external credential setup. Let us set up the named credential using the above external credential.

    Named Credential Setup - SalesforceCodex

    Put base API URL in Url property for named credential. If we have an API Url

    https://api.veriphone.io/v2/verify?phone=49-15123577723&key=266B0091BC9547A2A40DD088795FA4C6

    then only put https://api.veriphone.io and the rest of the URL will be appended using the Http Callput action. Add the above-created external credential to the External Credential property.

    4. Create Salesforce Flow to Verify Phone/Mobile

    Now let us create a screen flow Verify Phone that will validate the customer’s phone number and update the verification status in the account record.

    a. Get Current Record

    Create a recordId property of the account record type. We will get the current sObject record in this property. recordid is a dynamic variable that can hold record id as well as sObject.

    RecordId in Salesforce Flow

    b. Create a dynamic Action

    Now drag an Action element on the screen element. You will get + Create HTTP Callout (Beta) in the action selection dialog. We will get New HTTP Callout (Beta) screen to create a callout in flow.

     Create HTTP Callout (Beta)  - SalesforceCodex

    Put the required information in the HTTP Callout screen.

    (1) – API URL path. This will be appended to the base named credential Url that is set in the named credential.

    (2) – Required Url parameters. Values for these parameters are replaced using Flow variables.

    (3) – Provide Sample response JSON to create respionse Apex Class automatically.

    Provide sample response JSON by clicking on Add/Edit in Provide Sample Response section. This will create a response apex wrapper class.

    This process will create an external service VeriPhoneES that can be checked using Setup->External Services. It will also create a dynamic apex response class.

    Exteranl Service in Salesforce- SalesforceCodex

    c. Create a Response Object

    Let us create an element that will store the response after the HTTP callout action is performed. That response object will be used to get the status of phone verification.

    Dynamic Apex Response Object - SalesforceCodex

    d. Call API using Dynamic External Service

    Call dynamic external service in flow that was created after HTTP Callout (Beta) action was created. As per API, we have to pass the API key and Phone number that need to verify. The response is saved in the above-created response object.

    The API key can be saved in custom settings/custom metadata and can be populated from there. I have hardcoded it for demo purposes.

    e. Update Phone Verification using Update Element

    Based on the response object update status of the current account record phone verification.

    Account Phone Verification - SalesforceCodex

    e. Complete Flow

    Flow Http Callout - SalesforceCodex

    5. Test Flow

    Now everything is set up. Let us

    • Create an action button “Verify Phone using HTTP Method” in the account object and open the above flow Verify Phone on that button call.
    • Add created button in the respective page layout or the app builder page

    Test any account record where a phone number is entered. Click on the button “Verify Phone using HTTP Method” and check the verification status.

    References for Flow Http Callout

    HTTP Callout (Beta)

    Related Posts

    Verify Phone in Salesforce using VeriPhone API

    Dynamic Code Execution using Callable Interface

    Salesforce DropBox Integration to upload files

    Need Help?

    Need some kind of help in implementing this feature, connect on linked-in profile.

    call api in flow callout in flow comfirm in salesforce flow flow flow callout flow http callout HTTP Callout (Beta) http callout beta http callout in flow HTTP Callout into Flow HTTP Callout without Code HTTP Callouts from Flow integrate api in flow Invoking HTTP Callout lightning low code integration in flow no code integration in flow No-Code HTTP Web Callouts salesforce screen flow
    Share. Facebook Twitter Pinterest LinkedIn Tumblr Email
    Previous ArticleData Transformation with DataWeave in Salesforce Apex
    Next Article Shopify integration with Salesforce using Webhook
    Dhanik Lal Sahni
    • Website
    • Facebook
    • X (Twitter)

    With over 18 years of experience in web-based application development, I specialize in Salesforce technology and its ecosystem. My journey has equipped me with expertise in a diverse range of technologies including .NET, .NET Core, MS Dynamics CRM, Azure, Oracle, and SQL Server. I am dedicated to staying at the forefront of technological advancements and continuously researching new developments in the Salesforce realm. My focus remains on leveraging technology to create innovative solutions that drive business success.

    Related Posts

    By Dhanik Lal Sahni4 Mins Read

    How to Build a Generic Modal Window in Lightning Web Component

    May 26, 2025
    By Dhanik Lal Sahni6 Mins Read

    Top 10 Salesforce Flow Features of Salesforce Summer ’25

    May 11, 2025
    By Dhanik Lal Sahni6 Mins Read

    Unlock the Power of Vibe Coding in Salesforce

    April 30, 2025
    View 1 Comment

    1 Comment

    1. Pingback: Current Record in Salesforce Flow - SalesforceCodex

    Leave A Reply Cancel Reply

    Ranked #1 SALESFORCE DEVELOPER BLOG BY SALESFORCEBEN.COM
    Featured on Top Salesforce Developer Blog By ApexHours
    Recent Posts
    • How to Build a Generic Modal Window in Lightning Web Component
    • Top 10 Salesforce Flow Features of Salesforce Summer ’25
    • Unlock the Power of Vibe Coding in Salesforce
    • How to Implement Dynamic Queueable Chaining in Salesforce Apex
    • How to Implement Basic Queueable Chaining in Salesforce Apex
    Ranked in Top Salesforce Blog by feedspot.com
    RSS Recent Stories
    • How to Connect Excel to Salesforce to Manage Your Data and Metadata February 9, 2025
    • Difference Between With Security and Without Security in Apex January 2, 2025
    • Top Reasons to Love Salesforce Trailhead: A Comprehensive Guide December 5, 2024
    • How to Utilize Apex Properties in Salesforce November 3, 2024
    • How to Choose Between SOQL and SOSL Queries July 31, 2024
    Archives
    Categories
    Tags
    apex (111) apex code best practice (8) apex rest (11) apex trigger best practices (4) architecture (22) Asynchronous apex (9) AWS (5) batch apex (9) batch processing (4) code optimization (8) code review tools (3) custom metadata types (5) design principle (9) file upload (3) flow (15) future method (4) google (6) google api (4) integration (19) integration architecture (6) lighting (8) lightning (64) lightning-combobox (5) lightning-datatable (10) lightning component (30) Lightning web component (62) lwc (51) named credential (8) news (4) optimize apex code (4) Permission set (4) pmd (3) Queueable (9) rest api (23) S3 Server (4) salesforce (141) salesforce apex (46) salesforce api (4) salesforce api integration (5) Salesforce Interview Question (4) salesforce news (5) salesforce question (5) solid (6) tooling api (5) Winter 20 (8)

    Get our newsletter

    Want the latest from our blog straight to your inbox? Chucks us your detail and get mail when new post is published.
    * indicates required

    Ranked #1 SALESFORCE DEVELOPER BLOG BY SALESFORCEBEN.COM
    Featured on Top Salesforce Developer Blog By ApexHours
    Recent Posts
    • How to Build a Generic Modal Window in Lightning Web Component
    • Top 10 Salesforce Flow Features of Salesforce Summer ’25
    • Unlock the Power of Vibe Coding in Salesforce
    • How to Implement Dynamic Queueable Chaining in Salesforce Apex
    • How to Implement Basic Queueable Chaining in Salesforce Apex
    Ranked in Top Salesforce Blog by feedspot.com
    RSS Recent Stories
    • How to Connect Excel to Salesforce to Manage Your Data and Metadata February 9, 2025
    • Difference Between With Security and Without Security in Apex January 2, 2025
    • Top Reasons to Love Salesforce Trailhead: A Comprehensive Guide December 5, 2024
    • How to Utilize Apex Properties in Salesforce November 3, 2024
    • How to Choose Between SOQL and SOSL Queries July 31, 2024
    Archives
    Categories
    Tags
    apex (111) apex code best practice (8) apex rest (11) apex trigger best practices (4) architecture (22) Asynchronous apex (9) AWS (5) batch apex (9) batch processing (4) code optimization (8) code review tools (3) custom metadata types (5) design principle (9) file upload (3) flow (15) future method (4) google (6) google api (4) integration (19) integration architecture (6) lighting (8) lightning (64) lightning-combobox (5) lightning-datatable (10) lightning component (30) Lightning web component (62) lwc (51) named credential (8) news (4) optimize apex code (4) Permission set (4) pmd (3) Queueable (9) rest api (23) S3 Server (4) salesforce (141) salesforce apex (46) salesforce api (4) salesforce api integration (5) Salesforce Interview Question (4) salesforce news (5) salesforce question (5) solid (6) tooling api (5) Winter 20 (8)

    Get our newsletter

    Want the latest from our blog straight to your inbox? Chucks us your detail and get mail when new post is published.
    * indicates required

    Facebook X (Twitter) Instagram Pinterest YouTube Tumblr LinkedIn Reddit Telegram
    © 2025 SalesforceCodex.com. Designed by Vagmine Cloud Solution.

    Type above and press Enter to search. Press Esc to cancel.

    Ad Blocker Enabled!
    Ad Blocker Enabled!
    Our website is made possible by displaying online advertisements to our visitors. Please support us by disabling your Ad Blocker.