Skip to content

Talk to an integration expert today on 0191 820 1484

Zynk

Developer

HTTP Integration

Zynk's HTTP integration lets a workflow call web services that Zynk has no dedicated connector for. The HTTP Task sends GET, POST, PUT, PATCH, DELETE and HEAD requests to REST, SOAP and XML-RPC endpoints, saves the response, and passes it to the tasks that update Sage, Xero, Business Central or your other systems.

Available for
Workflow

Capabilities may differ depending on the product.

Book a callSee what you can do

Benefits

Why businesses connect HTTP

Reach systems without a connector

Bespoke portals, niche industry platforms and in-house apps often have an API but no off-the-shelf connector. HTTP requests let Zynk read from and write to them alongside the systems it already supports.

Every common method

Use GET to fetch data, POST or PUT to create and replace records, PATCH to change part of one, DELETE to remove it and HEAD to check a resource. REST, SOAP and XML-RPC services are all within reach.

Headers, forms and basic authentication

Set custom headers such as Content-Type or an authorisation token, submit form values, or sign in with HTTP basic authentication. The request body can come from a file produced earlier in the workflow.

Responses saved for the next step

The response body is written to a file, and headers can be saved as XML. JSON or XML responses are then converted and mapped like any other data, ready for an import task.

Retries and time limits

A retry count and timeout on each request help a workflow ride out a slow or briefly unavailable server, and failures show up in the workflow log so you can see exactly which call went wrong.

Capabilities

What you can do with HTTP

Every task the Zynk HTTP connector can run, grouped by the direction data moves.

Actions in HTTP

Tasks Zynk can automate in HTTP

1 task

  • HTTP task → in HTTP

Need something that isn't listed?

Most HTTP projects include at least one custom step. Our team builds it for you.

Talk to us

The problem

Why integrate HTTP?

Many businesses rely on at least one system Zynk has no named connector for: a carrier's tracking service, a payment provider, a supplier portal or an app built in-house. Without a way to call its API, data moves by export, email and rekeying, or a developer writes and nurses a one-off script.

Without integration

  • One-off scripts written to call an API, then forgotten until they break
  • Data from a web service exported by hand and loaded elsewhere
  • Updates to a partner system made through its web screens
  • A failed call nobody notices until a customer complains

With Zynk

  • API calls live inside a managed, scheduled Zynk workflow
  • Responses are saved, converted and imported automatically
  • POST, PUT and PATCH requests send changes straight to its API
  • Retries, timeouts and logs make failures visible

How it works

How the HTTP integration works

  1. Step 1: Start from the API documentation

    Note the endpoint URL, method, required headers, authentication and the body format the service expects, whether JSON, XML or form values. The service's own documentation is the reference for all of it.

  2. Step 2: Build the request

    Configure the HTTP Task with the URL, method and headers. Earlier tasks can generate the body, for example converting a Sage export to JSON with the XML To JSON task.

  3. Step 3: Handle the response

    Save the response body and headers to files, convert JSON to XML where needed, and map the result into the connector that should receive it, such as Xero or Business Central.

  4. Step 4: Schedule and monitor

    Run the request on a schedule or as one step in a larger integration. Retry settings smooth over brief outages, and the workflow log shows which request failed and when.

Integrations

What can you connect to HTTP?

JSONSage 200XeroMicrosoft Dynamics 365 Business CentralXML and XSLTHTMLWebSage 50 UKShopifySalesforce

HTTP and JSON

Build JSON request bodies from workflow data with XML To JSON, and turn JSON responses back into XML with JSON To XML so they can be mapped.

From HTTP to JSON:JSON responsesFrom JSON to HTTP:JSON request bodies

View the JSON integration →

HTTP and Sage 200

Fetch orders from a bespoke trade portal's API and import them into Sage 200 as sales orders, then post Sage 200 stock levels back to the portal.

From HTTP to Sage 200:Sales ordersFrom Sage 200 to HTTP:Stock levels

View the Sage 200 integration →

HTTP and Xero

Send Xero invoices to a payment or collections service that Zynk has no connector for, and record the payments it reports back in Xero.

From HTTP to Xero:PaymentsFrom Xero to HTTP:Invoices

View the Xero integration →

HTTP and Microsoft Dynamics 365 Business Central

Post Business Central sales shipments to a carrier or customer API, and import orders returned by an external service as Business Central sales orders.

From HTTP to Microsoft Dynamics 365 Business Central:Sales ordersFrom Microsoft Dynamics 365 Business Central to HTTP:Shipments

View the Microsoft Dynamics 365 Business Central integration →

Find your integration →

HTTP integration FAQs

Can Zynk connect to any REST API?
In most cases, yes. The HTTP Task can call REST, SOAP and XML-RPC services with the usual methods, custom headers and basic authentication. Services that need a more involved sign-in flow may need extra steps, which our team can assess with you.
Which HTTP methods does the HTTP Task support?
GET, POST, PUT, PATCH, DELETE and HEAD. GET normally fetches data and POST sends it, while PUT, PATCH and DELETE suit APIs that create, change and remove records. HEAD returns only the headers, which is handy for checks.
Can the HTTP Task send JSON?
Yes. Set the Content-Type header to application/json and supply the body from a file or the contents field. Zynk's JSON connector can build that body from XML and convert JSON responses back to XML for mapping.
Does the HTTP Task follow redirects?
No. The task does not follow HTTP redirects, so the URL in its settings must be the final address of the endpoint. If a service redirects, check its documentation for the direct URL and use that one instead.
How does the HTTP Task handle errors and timeouts?
Each request has a timeout, two minutes by default, and a retry count for connection errors. If the server still fails, the error is reported in the workflow log, so you can see which call failed and why.
When should I use HTTP instead of a dedicated connector?
Use a dedicated connector when one exists, because it already knows the system's records and quirks. HTTP is for everything else: in-house apps, niche platforms, or a single API call that a standard connector does not cover.
Can I call a SOAP web service from Zynk?
Yes. Send a POST request with the SOAP envelope as the body and the headers the service expects, such as Content-Type and any SOAP action. The XML response is saved to a file and can be read by XSLT or mapped like any other XML.

See what Zynk can automate for your HTTP setup

Book a 20-minute call. We'll review your systems, flag the quick wins and outline a practical route to going live.

Book a callSee pricing