> ## Documentation Index
> Fetch the complete documentation index at: https://docs.alumio.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Marello
> Connect Alumio to Marello.
## Extra information
System documentation:
## Connector package documentation
# Setting up HTTP Client Marello
## Steps
1. In Alumio Dashboard, go to Clients > HTTPS Client. Create a new HTTP Client and select Marello HTTP Client as the prototype of the HTTP Client.
2. Fill in the Base URI, Authentication Type, Client ID, Client Secret, and Scopes (Optional).
3. Press “Grant access to Marello CRM”.
4. Save when the Key is already provided.
# Subscribing to Entities from Marello
## Steps
1. Go to Connections -> Incoming and create a new incoming configuration and select Marello Subscriber as the subscriber.
2. Select the entity you want to subscribe from Marello.
3. Add any request parameters needed to subscribe to the entity (optional).
4. You can optionally add a transformer to transform the request parameters into something you need.
5. Select the Marello HTTP Client to use.
## General Concept
We follow Marello documentation on building this connector so you can easily use the connector based on Marello API Reference.
**Entity**
It’s the entity you want to subscribe from Marello. Please refer to the entities in Management APIs from Marello API Reference page.
**Request Parameters**
These are the parameters you can provide to get the needed entity based on Marello API Reference. Please look at the example below on how to fill Request Parameters field when subscribing Single Request entity
That’s why we need to define **id** property inside **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 Retrieve a specific country record entity.
/api/countries/AD
**Input Transformer**
Any transformer’s set here will be executed after the Request Parameters 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 Marello.
# Publishing Entity to Marello
## Steps
1. Go to Connections -> Outgoing, create a new outgoing configuration and select Marello Publisher as the publisher.
2. Select the action that you want the publisher to do with the data.
3. Select the Marello entity you want the data to be published to.
4. 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 Create (HTTP POST method), PATCH (HTTP PATCH method), and Delete (HTTP DELETE method).
**Entity**
We support publishing to most Marello endpoints but not with publishing binary files at the moment. Please refer to the entities in Management APIs from Marello API Reference page. Based on the documentation, some endpoints may need one or more path parameters.
For endpoints that require object as the request payload, please look at the example below. For example, we want to Create a new customer record. Please select “Create” as the action and “Create a new customer record” as the entity of the publisher.
You can put the payload you want to send to Marello into payload property in the data. Here is an example of the Possible Response after Creation.
Alumio will send an API request to Marello with URL
/api/marellocustomers
**HTTP Client**
It’s the HTTP Client configuration or prototype you will use to access Marello.