Skip to main content
Version: 1

Make HTTP Call

  • Category

    • API

    • Outbound

    • Integration

    • POST, PUT, PATCH, GET,DELETE,HEAD

  • Flow Icon

Overview

The Make HTTP Call component in Plinqx is a versatile tool designed for outbound integration calls to external systems. It supports various HTTP methods, allowing you to configure the request headers, query parameters, and body as needed for your integration requirements.

Note: Ensure you have configured your named credentials in Salesforce before using this component, as it relies on them for secure API interactions.

Inputs

  1. **URL/Endpoint: **Provide the full URL path, including parameters (e.g., https://domain/path).

  2. Named Credential:

    Select from a dropdown list of all configured and active named credentials in your Salesforce org.

  3. HTTP Method:

    Choose from a dropdown list of HTTP methods (GET, POST, PATCH, DELETE, HEAD, etc.).

  4. Timeout in ms:

    Specify the timeout duration for the HTTP callout, if necessary.

  5. Params:

    A list of key-value pairs representing query parameters to be appended to the URL.

  6. Headers:

    A list of key-value pairs for setting standard HTTP headers.

  7. Body:

    The JSON payload to send in the request.

  8. Compress Body:

    Enable to compress the request body before sending.

  9. Set Body as Blob:

    Enable to convert the body into a binary large object (blob) before sending.

  10. Close Transaction:

    Enable to indicate that the callout should run in its own transaction.

Outputs

  1. Body:

    The response body from the callout.

  2. Collection of Headers:

    The headers returned in the callout response.

  3. Error Message:

    Any HTTP error or success message received.

  4. Status:

    The textual HTTP status returned.

  5. Status Code:

    The numerical HTTP status code returned.

Example Scenario - Syncing Order Details to External Shipping Service

Scenario Overview:

A Salesforce org needs to send order details to an external shipping service for processing and dispatch. The order information, including shipping address and items, needs to be transmitted securely upon order confirmation.

Implementation with Make HTTP Call Component:

  1. Flow Setup for Order Processing:

    • Create a Salesforce flow that triggers when an order is confirmed in the org.
  2. Adding Make HTTP Call Component:

    • Incorporate the Make HTTP Call component to send the order details to the shipping service's API.
  3. Configuring Inputs:

    • 'URL/Endpoint' is set to the shipping service's API endpoint.

    • 'Named Credential' is selected to authenticate the call securely.

    • 'HTTP Method' is chosen as POST for sending order data.

    • 'Body' contains the JSON payload with the order details.

    • Other inputs like 'Headers' and 'Params' are configured as required by the shipping service's API.

  4. Executing API Call:

    • The flow processes the order confirmation and executes the HTTP call, sending the order details to the shipping service.
  5. Handling API Response:

    • The response 'Body' and 'Status Code' are evaluated to confirm successful transmission.

    • Any 'Error Message' received is logged for troubleshooting.

Results:

Implementing the Make HTTP Call component allows the Salesforce org to securely and efficiently send order details to the external shipping service. This approach ensures real-time data synchronization, enhancing the efficiency of the order fulfillment process and improving overall customer service.