In n8n, click the "Add workflow" button in the Workflows tab to create a new workflow. Add the starting point – a trigger on when your workflow should run: an app event, a schedule, a webhook call, another workflow, an AI chat, or a manual trigger. Sometimes, the HTTP Request node might already serve as your starting point.
Create custom HTTP Request and Sellix workflows by choosing triggers and actions. Nodes come with global operations and settings, as well as app-specific parameters that can be configured. You can also use the HTTP Request node to query data from any app or service with a REST API.
Get current shop
Retrieve details about the current shop.
Create payment
Initiate a new payment process.
Complete payment
Finalize a previously initiated payment.
Cancel payment
Abort an ongoing payment process.
Get order
Retrieve details about a specific order.
List orders
Retrieve a list of all orders.
Replace orders
Replace an existing order with new data.
Update orders
Modify the details of an existing order.
Update custom fields
Updates custom fields for an existing order.
Get customer
Retrieve details about a specific customer.
Create customer
Add a new customer to the system.
List customers
Retrieve a list of all customers.
Update customer
Modify the details of an existing customer.
Get subscription
Retrieve details about a specific subscription.
Create subscription
Add a new subscription to the system.
List subscriptions
Retrieve a list of all subscriptions.
Cancel subscription
This endpoint cancels an existing subscription.
Check license
This endpoint checks the validity of a license.
To set up Sellix integration, add the HTTP Request node to your workflow canvas and authenticate it using a generic authentication method. The HTTP Request node makes custom API calls to Sellix to query the data you need using the API endpoint URLs you provide.
See the example hereThese API endpoints were generated using n8n
n8n AI workflow transforms web scraping into an intelligent, AI-powered knowledge extraction system that uses vector embeddings to semantically analyze, chunk, store, and retrieve the most relevant API documentation from web pages. Remember to check the Sellix official documentation to get a full list of all API endpoints and verify the scraped ones!
Save engineering resources
Reduce time spent on customer integrations, engineer faster POCs, keep your customer-specific functionality separate from product all without having to code.
Learn more
Supercharge your CRM
Need a more powerful integration with your CRM? n8n lets you go beyond standard integrations offered by popular CRMs!
Learn more
Discover our latest community's recommendations and join the discussions about HTTP Request and Sellix integration.
Moiz Contractor
Describe the problem/error/question Hi, I am getting a - Google hasnt verified this app error. I have Enable the API, the domain is verified on the Cloud Console, the user is added in the search console and the google do…
Open topic
theo
Describe the problem/error/question I a http request node, I use a Google service account API credential type. I need the “Impersonate a User” field to be dynamic, pulling data from the “email” field in the previous nod…
Open topic
Jon
Describe the problem/error/question I have a simple workflow that retrieves an image from url with http node and prints the json/binary in code. I have a few logs, but I am confused why I see duplicate messages for each …
Open topic
Dan Burykin
Hi! I’m still in the beginning. Now I need to make an API call via HTTP node, and send all static parameters, but with the array of emails parameter (named it wrongly just to show what I need {{ $json.email[all] }}). Wo…
Open topic
Tony
Hi! I have a question: I am making an app that allows a person to scrape some data via a Python library. I have a Python script that needs to be triggered after certain user actions. What is the best way to: Send a p…
Open topic
The world's most popular workflow automation platform for technical teams including
Build complex workflows, really fast