Extra information
System documentation: Lime CRM API ReferenceConnector package documentation
Table of Contents
- 1. Setting up HTTP Client Lime CRM
- 1.1 Steps
- 2. Subscribing to entities from Lime CRM
- 2.1 Steps
- 2.2 General concept
- 3. Publishing entity to Lime CRM
- 3.1 Steps
- 3.2 General concept
1. Setting up the HTTP Client Lime CRM
1.1 Steps- In the Alumio Dashboard, go to Clients -> HTTP Clients. Create a new HTTP Client and select Lime CRM Client as the HTTP Client.
- Fill in the Base URI and X API Key. (For more information, see Lime CRM Authentication Reference)
- You can optionally enable logging of request to get the log of the authentication.
- Save the HTTP Client for use.

2. Subscribing to Entities from Lime CRM
2.1 Steps- Go to Connections -> Incoming and create a new incoming configuration and select the Lime CRM Subscriber as the subscriber.
- Select the Lime CRM HTTP Client to use.
- Select the entity you want to subscribe to from Lime CRM.
- Add any request parameters needed to subscribe to the entity.
- (Optional) Add a transformer to modify the request parameters into something you will request from Lime CRM.
- (Optional) Enable pagination to allow Alumio to fetch paginated entities.



- “Path” is the path parameter of the url. For example the {id}.
- “Query” is a defined set of parameters attached to the end of a URL.
Example: www.url.com?type=true&start=0
3. Publishing Entity to Lime CRM
3.1 Steps- Go to Connections -> Outgoing, create a new outgoing configuration and select Lime CRM Publisher as the publisher.
- Select the Action that you want the publisher to perform with the data.
- Select the Lime CRM entity you want the data to be published to.
- (Optional) Add any path data to the request on the key path.
- (Optional) Add any query data to the request on the key query.
- (Optional) Add any payload data to the request on the key payload.
- Select the HTTP Client to use.




- “Path” is the path parameter of the URL. For example the {id}.
- “Query” is a defined set of parameters attached to the end of a URL.
Example: www.url.com?type=true&start=0 - “Payload” is the data contained within a request.