Extra information
System documentation: Lead Gen & CRM API Reference Lead Gen & CRM Connector Package DocumentationSetting up HTTP Client Lead Gen & CRM
Steps
- In the Alumio Dashboard, go to Clients > HTTP Client. Create a new HTTP Client and select Lead Gen & CRM HTTP Client as the prototype of the HTTP Client.
- Fill in the Base URI (Example: http://api.yourappdomain.com/pubapi).
- Choose the version and Fill the AccountID & SrcretKey
- Enable the logging (Optional but recommended)
- Save and Continue.

Subscribing to Entities from Lead Gen & CRM
Steps
- Go to Connections -> Incoming, create a new incoming configuration, and select Lead Gen & CRM - Subscriber as the subscriber.
- Select the entity to subscribe to Lead Gen & CRM.
- Add any request parameters and the Payload needed to subscribe to the entity.
- You can optionally add a transformer to transform the request parameters into something you need.
- Select the Lead Gen & CRM Client to use.
General Concept
We follow Lead Gen & CRM documentation on building this connector, so you can easily use the connector based on Lead Gen & CRM API Reference. Entity It’s the entity from Lead Gen & CRM you want to subscribe to. Please refer to the entities in Management APIs from the Lead Gen & CRM API Reference page. Request Parameters You can provide these parameters to get the needed entity based on Lead Gen & CRM API Reference. Please look at the example below on how to fill the Request Parameters field when subscribing to Leads entities.

Publishing Entity to Lead Gen & CRM
Steps
- Go to Connections -> Outgoing, create a new outgoing configuration, and select Lead Gen & CRM Publisher as the publisher.
- Select the action you want the publisher to do with the data.
- Select the Lead Gen & CRM entity where the data will be published.
- You can optionally add any query parameters to the request.
- You can also optionally add transformers to transform the data into anything you need before submitting it to Lead Gen & CRM.
- Select the HTTP Client to use.

General Concept
Like the subscriber, the publisher has similar methods for using it. The difference is the payload that will be submitted by the publisher originating from the data (from routes and transformers in outgoing configuration). Entity We support publishing to most Lead Gen & CRM REST endpoints. Please look at the example below for endpoints that require an object as the request payload. For example, we want to update the Lead data.
