Skip to main content
Version: 2

Build an Outbound Integration

info

Available: Starter and Premium

Introduction​

Creating an outbound integration in Salesforce using Plinqx involves configuring your system to send data from Salesforce to external systems or services. This process requires careful planning and understanding of both Salesforce and Plinqx functionalities.

Preparation and Design Review​

  • Begin by thoroughly reviewing and documenting your design decisions. Ensure that your integration strategy aligns with business requirements and technical capabilities.

  • Consider factors like data volume, frequency of data transfer, and security requirements in your design.

Accessing Plinqx Management Console​

  • Navigate to the Plinqx Management Console within Salesforce. This is your central hub for creating and managing integrations.

Creating a New Integration​

  1. Initiating Integration Setup:

    • Click the ‘New’ button to start setting up your outbound integration.

  2. Selecting Event Type:

    • Choose the type of event that will trigger your outbound integration. For outbound integrations, typically ‘Object Event’ is selected. This refers to changes in Salesforce objects (like creation or updates) that will trigger data transmission.

    • Ensure you understand the different

  3. Defining Integration Details:

    • Provide a meaningful name, category (for organization in the management console), and a description for your integration. These details are crucial for easy identification and management within the Plinqx console.

  4. Selecting Salesforce Object:

    • Choose the Salesforce object that will be the source of the data for the outbound integration. This selection is critical as it defines which data will be sent out.

  5. Configuring Event Rule Type:

    • Determine the event rule type – ‘All or Nothing’ or ‘Criteria Based’. This setting governs when the integration is triggered.

    • Specify the record type if applicable, and select when the event should execute (Insert, Update, Delete, Undelete).

  6. Setting Up Named Credential:

    • Choose the named credential for secure API communication. Named credentials are a best practice for managing external API integrations in Salesforce. Review Salesforce’s

  7. URL Parameters and Payload Configuration:

    • Add additional URL parameters if needed. Remember to start your parameters with a forward slash '/' and use wildcards appropriately.

    • Choose your payload type – Standard, Custom, Apex (using a custom Apex class), Plinqx Mapping, or Flow. This decision impacts how data is formatted and sent.

  8. Activation and Deployment:

    • Decide whether to activate the integration immediately upon deployment. It can be beneficial to initially leave it inactive for testing purposes.

    • Click ‘Next’ to deploy your outbound integration.

Conclusion​

Outbound integrations built with Plinqx in Salesforce are a powerful way to extend your CRM capabilities and sync your Salesforce data with external systems. By following these steps and utilizing the Plinqx tools effectively, you can create robust, secure, and efficient outbound integrations that align with your business objectives.

Building Custom Outbound Integration with Plinqx Flow Components​

Introduction​

Custom outbound integrations in Plinqx extend beyond record-triggered events, offering a more tailored approach to meet specific integration needs. By leveraging the versatility of Plinqx Flow Components, you can design integrations that are precisely aligned with your business processes and external system requirements.

Key Components for Custom Outbound Integrations​

  1. Data Transformation Components:

    • Essential for preparing and formatting data before sending it to external systems. These components can handle various data formats (like JSON, XML) and transform Salesforce data into the structure required by the external system.

  2. HTTP Request Components:

    • Facilitate the actual sending of data to external APIs. These components can configure and execute HTTP requests (GET, POST, PUT, DELETE) using named credentials for secure and efficient API communication.

  3. Error Handling Components:

    • Critical for managing any errors that occur during the outbound data transmission process. These components can log errors, retry failed requests, or trigger alternative processes in case of failures.

  4. Logging Components:

    • Provide a way to record the details of outbound transactions, including successes and failures. This is crucial for monitoring the integration's performance and for troubleshooting issues.

  5. Notification Components:

    • Useful for sending alerts or notifications based on the outcome of the outbound process. For instance, if a data sync fails or encounters issues, these components can trigger email alerts or create task records for follow-up.

Flexibility and Customization​

  • Plinqx’s Flow Components are designed to be highly customizable, allowing you to adjust their functionality to fit the specific requirements of your outbound integration scenario.

  • Whether it’s a simple data push to an external system or a complex integration involving multiple steps and conditional logic, these components provide the building blocks to construct your desired workflow.

Integration Design Considerations​

  • When designing your custom outbound integration, consider factors like data volume, frequency of updates, real-time vs. batch processing, and the need for data transformation.

  • Map out the entire flow of data, from the point of extraction in Salesforce to the final transmission to the external system, utilizing the appropriate Plinqx components at each stage.

Conclusion​

Custom outbound integrations using Plinqx Flow Components offer a powerful and flexible solution to meet your unique business and technical requirements. By strategically selecting and configuring these components, you can build efficient, reliable, and scalable outbound integrations that seamlessly connect Salesforce with your external business systems.