Skip to main content
Facilita is the CRM where a developer’s sales team tracks deals, customers, projects, units and tasks. Connecting Facilita to Morada OS lets you ask about all of that in plain language (“how many deals are in Proposal?”) and get the answer with a link that opens each record directly in Facilita.

​
Before you start

Access to Morada OS

An active account on os.morada.ai, with your company’s corporate login.

The Facilita key belongs to the company

Facilita sells one key per company, with an activation fee and a monthly charge. It is not on a Facilita screen and nobody on the team has one of their own: whoever administers the company account receives the key from Facilita itself. It is stored once, by your company. Who gets to use the connector, though, is decided person by person.
If Morada already integrates your Facilita, the key was requested from Facilita on your company’s behalf and Morada sets everything up for you. The key is already stored. If your company bought the key straight from Facilita, whoever administers Morada OS stores it once, in the step below. Either way, an administrator still has to release each person who will use Facilita.

​
For the administrator: store the key and release the people

Two steps, and the second one is what grants access. Storing the key releases nobody, not even you.
1

Store the company key

In the sidebar, click Conectores (Connectors), open the Facilita card and go to its Administração (Administration) tab. Fill in:
  • Instância (instance): just your company’s account name, without the rest of the address. If you sign in at yourdeveloper.facilitavendas.com, type yourdeveloper.
  • API Key: the key your company received from Facilita.
  • Token do usuário (user token): the token that came with it.
On save, Morada OS checks the three values with Facilita right away. When the key is refused, the screen says so and asks you to check the instance, the API Key and the user token: the refusal arrives the same way for all three, so nothing can say which one is wrong. Start with the instance, which is where most mistakes are: the account name alone, without .facilitavendas.com and without https://. You fix it without typing everything again.Replacing or removing the key does not change who you released. With no key stored, nobody uses Facilita; when you store one again, the same people come back, with the same links and the same tools, without you releasing everyone a second time. To actually take somebody’s access away, use Remover acesso (remove access) on their row: that is the only thing that removes it.
2

Release people, one at a time

Once the key is stored, the list Quem pode usar o Facilita (who can use Facilita) appears, holding your company’s people in Morada OS. Nobody joins that list on their own, you included: click Liberar (release) on the row of each person who should have access.A released person sees Facilita in the chat immediately, with nothing to fill in. Anyone not released does not see the connector at all.To take access away later, use Remover acesso (remove access) on that person’s row.
3

Link whoever needs it (optional)

You may release anyone at the company, whether or not they have a Facilita account. The key belongs to the company, so queries work for everyone you release.A link is only needed for what depends on who the person is inside Facilita. Today that is one single thing: the question “who am I in Facilita”. Tomorrow it will be the actions that record something in their name.When the person’s login e-mail also exists in Facilita, Morada OS suggests the link and applies it automatically on release. When it does not, the row shows Sem vínculo no Facilita: consultas funcionam, ações em nome dela não, and you can use Vincular (link) to pick the matching Facilita user. Desvincular (unlink) undoes the link without taking access away.
4

Choose each person's tools

Every released row shows Ferramentas · todas (tools, all of them). Open it and switch off whatever that person should not use; the change applies to them alone.One difference worth knowing: someone on todas (all) automatically gains any new tool Facilita gets in Morada OS. Someone on a list you picked keeps exactly what you ticked, even after a new tool arrives.
The key is stored encrypted and Morada OS never shows it back, not even to whoever stored it. The screen shows only that a key exists, who stored it and when. Nobody on the team types any key.

​
What it looks like for each person on the team

There is nothing to fill in, and there is no Connect button for Facilita. Once an administrator releases you, the Facilita card appears in Conectores ready to use, saying who released it. From then on you just ask in the chat.
Why do you not type your e-mail? Because a typed e-mail could be a colleague’s, and the assistant would start acting as if you were that person. Who you are in Facilita is decided by Facilita itself: Morada OS looks your login e-mail up in your company’s user list there, or the administrator points at your record.

​
If the Facilita card is not there

Either your company has not stored the key yet, or you have not been released. Both are fixed by whoever administers Morada OS at your company (or by Morada, if they set the integration up). There is nothing you can fill in to solve it on your own. You were released, but Morada OS does not know which record is yours over there. Queries work normally: deals, customers, projects, tasks, all of it. Only the question “who am I in Facilita” stays out, and the assistant says so instead of guessing. Ask your administrator for the link.

​
If the card says the access needs attention

Facilita refused the company key, usually because it was replaced or cancelled on the Facilita side. While that lasts, the assistant does not read Facilita and says so in the chat instead of answering over it. It is fixed by whoever administers the account (or by Morada, if they set the integration up), storing the new key. As soon as it lands, everyone already released comes back on their own.

​
What the assistant can do

In this version the connector is read-only: the assistant reads Facilita and never writes anything into it.
Three things Facilita’s API cannot filter, and the assistant says so instead of making it up: “my deals” (Facilita does not filter deals by owner; ask for the count per stage or for a deal by customer), “my tasks” (ask by period or by status) and customer searches beyond the first 15 (refine the term with the full name, the e-mail or the mobile digits).

​
Adjusting permissions on your card

Among the tools the administrator released to you, open Conectores > Facilita and you will see the list What Morada OS can read, with a permission tag on each tool:
  • Always allow: the tool runs right away whenever your request needs it. It is the default, because none of them changes Facilita.
  • Ask first: the assistant asks for your confirmation in the chat before reading.
Nothing runs on its own outside that list: there is no automatic routine, schedule or background sync. The assistant only touches your Facilita when you ask, in the conversation.

​
Everyday use

Phone numbers and CPF are your customers’ personal data. Use them in the chat only to locate the record in Facilita, inside your company’s account, and do not copy them out of Morada OS or into conversations shared with people who do not need them.
Want better results? Read How to ask well: three minutes that improve every request you make.

​
How access is taken away

An administrator takes it away: in Conectores > Facilita > Administração, Remover acesso on that person’s row. Facilita drops out of their chat immediately, and the administrator can release them again later. You do not need to (and cannot) unlink your own account, because there is no account of yours stored here: there is one key, and it is the company’s. If you want to stop using Facilita, ask for your access to be removed.