Add topics about this connector package here.
Always check the ‘How to use the Alumio connector packages’ topic.
Extra information
System documentation:
Connector package documentation
Webflow
Setting up HTTP Client Webflow
Steps
- In Alumio Dashboard, go to Clients > HTTPS Client. Create a new HTTP Client and select Webflow HTTP Client as the prototype of the HTTP Client.
- Fill in the Base URI, and Authentication Type
- Oauth2
- Fill in Client ID, Client Secret, and Scopes (V2 only).
- Press “Grant access to Webflow”.
- Token (V1 only)
- Fill in the Token
- Save.
Subscribing to Entities from Webflow
Steps
- Go to Connections → Incoming and create a new incoming configuration and select Webflow Subscriber as the subscriber.
- Select the entity you want to subscribe from Webflow.
- Add any request parameters needed to subscribe to the entity (optional).
- You can optionally add a transformer to transform the request parameters into something you need.
- Select the Webflow HTTP Client to use.
General Concept
We follow Webflow documentation on building this connector so you can easily use the connector based on Webflow API Reference.
Entity
It’s the entity you want to subscribe from Webflow. Please refer to the entities in Management APIs from the Webflow API Reference page.
Request Parameters
These are the parameters you can provide to get the needed entity based on Webflow API Reference. Please look at the example below on how to fill the Request Parameters field when calling “Retrieve Get Collection Details” entity
That’s why we need to define the collection_id property inside the path property in the Request Parameters field. The properties inside query parameters will be parsed as query parameters. Here is the final URL that will be called when using such Request Parameters field on the Retrieve Get Collection Details.
/v2/collections/321321
Input Transformer
Any transformers set here will be executed after the Request Parameters are loaded. So, you basically can add any transformer to provide and transform the request parameters into anything you need either as path parameters and/or as query parameters of an entity.
HTTP Client
It’s the HTTP Client configuration or prototype you will use to access Webflow.
Publishing Entity to Webflow
Steps
- Go to Connections → Outgoing, create a new outgoing configuration, and select Webflow Publisher as the publisher.
- Select the action that you want the publisher to do with the data.
- Select the Webflow entity you want the data to be published.
- Select the HTTP Client to use.
General Concept
Like the subscriber, the publisher has similar methods on how to use it. The difference is the payload that will be submitted by the publisher originating from the data (from routes, from transformers in outgoing configuration).
Action
Currently, we support Post (HTTP POST method), Patch (HTTP PATCH method), Put (HTTP PUT method), and Delete (HTTP DELETE method).
Entity
We support publishing to most Webflow endpoints. Please refer to the entities in Management APIs from the Webflow API Reference page. Based on the documentation, some endpoints may need one or more path parameters.
For endpoints that require an object as the request payload, please look at the example below. For example, we want to Delete Collection Field. Please select “Delete” as the action and “Delete Collection Field” as the entity of the publisher.
You can put the payload you want to send to Webflow into the payload property in the data. Here is an example of the Possible Response after Creation.
Alumio will send an API request to Webflow with URL /v2/collections/321321/fields/111
HTTP Client
It’s the HTTP Client configuration or prototype you will use to access Webflow.