GET integration

Feature Snapshot

Summary:
GET integration in LeadConduit is a mechanism that sends or retrieves lead data using the HTTP GET method by appending data as URL query parameters. This method enables a lightweight and simple connection between LeadConduit and external systems.

Key Benefits:

• Simple implementation using standard URL query strings
• Easy testing—copy the URL into a browser for quick debugging
• Low overhead ideal for scenarios with limited connectivity or minimal data transfer requirements

Typical Use Cases:

• Retrieving data from external systems with read-only endpoints
• Submitting lead information when POST requests are not supported or desired
• Performing quick lookups or validations using parameter-based information

How the GET integration works?

Step‑by‑Step Instructions

1. Access the Flow Editor:
   Log into your LeadConduit account and navigate to the flow where you want to add GET integration.

2. Add an Integration Step:
   In the flow editor, click on Add to Flow > Integration, then choose the GET integration option.

3. Configure the GET Request:
   Enter the target URL where the GET request will be sent. Map LeadConduit fields to URL query parameters (for example, map the lead’s email to the “email” parameter) and include any static parameters as needed.

4. Set Optional Authentication or Additional Parameters:
   If the external endpoint requires authentication or specific keys, include these by appending them as additional query parameters.

5. Save and Test the Integration:
   Save the integration step and submit a test lead to verify that the GET request is generated correctly and that the endpoint responds with an expected HTTP 200 status and data payload.

Expected Result:
LeadConduit sends a GET request to the specified URL with the correct query parameters, and you receive a successful response (HTTP 200) along with any returned data.

Validation & Monitoring (optional)

• Test the Setup: Submit a test lead (e.g., email: user@example.com, phone: 555-0100) and ensure that a GET request is triggered, returning HTTP 200 and the expected data.
• Where to Monitor?: Check the Integration Logs in your LeadConduit flow events as well as any external system logs or API dashboard provided by the target endpoint.

Best Practices

• Always use HTTPS in the GET URL to secure data during transit.
• Avoid sending sensitive or large amounts of data via URL parameters since URLs can be logged or cached.
• Keep the number of query parameters minimal to prevent issues with URL length or encoding.
• Test the integration under different scenarios (e.g., missing or special-character data) to ensure robustness.
• Monitor HTTP response codes closely and handle common error codes (like 400 or 405) using appropriate troubleshooting steps.

Troubleshooting

Frequently Asked Questions (FAQ)

What is the GET integration used for?

GET integration reliably sends lead data as URL query parameters to an external endpoint, or retrieves data from a read-only service endpoint that supports GET requests.

Why choose GET integration over POST integration?

GET integration is simpler to implement and test; you can verify the output easily using a browser. It is best suited for simple data transmissions where secure and large payloads are not required.

How can I secure data sent through a GET integration?

Use HTTPS to encrypt data in transit and avoid including highly sensitive information in the URL since URLs might be logged or cached.

Can I include authentication with GET integration?

Yes, if the external endpoint requires authentication, include the necessary API keys or tokens as additional query parameters in the URL securely.

What should I do if my GET integration returns an error such as “405 Method Not Allowed”?

This error suggests that the endpoint does not accept GET requests. Confirm the method allowed by the target endpoint and adjust the integration method accordingly.

Glossary

• get-mapping.png200 KB