Summarize Content With:
Chatbots can do a lot today: answer questions, qualify leads, replace forms. But some conversations belong on the phone. The callback after an inquiry, the appointment confirmation, the quick follow-up when someone gets stuck in chat. Until now, that meant exporting data from your chatbot, storing it somewhere and triggering the call separately.
With the Famulor plugin for Dify, both happen in one workflow. Your Dify agent qualifies the lead in chat, creates the contact, places a real call with your Famulor assistant and then reads the summary and transcript back in. This article shows what the plugin does, what a typical flow looks like and how to set it up in four steps.
What's new? #
The Famulor plugin is now available in the Dify Marketplace. The plugin ID is famulor/famulor, and the current version is 0.1.1. The source code is public on GitHub.
Your Dify agents, chatflows and workflows can now work directly with your Famulor workspace: list assistants, start outbound calls, read call results and transcripts, create contacts and start campaigns.
What the plugin does: 7 tools #
| Tool | What it does |
|---|---|
| List Assistants | Lists the voice assistants in your workspace (ID, name, status). |
| Start Outbound Call | Places a real outbound phone call with an assistant. |
| Get Call | Reads a call's status, summary, post-call analysis and transcript. |
| List Calls | Lists recent calls, filtered by assistant, campaign or status. |
| Create Contact | Creates a contact (lead) by phone or email, or merges it with an existing one. |
| List Campaigns | Lists your outbound campaigns and their status. |
| Start Campaign | Starts a campaign. This begins real outreach to its leads. |
You can use the tools in an agent that decides on its own when to call which tool, or add them as fixed steps in a workflow.
Use case: from chat to callback with transcript #
A typical scenario: a Dify chatbot runs on your website. A prospect asks questions, the bot spots real interest and offers a callback. Here's the flow:
- Qualify the lead in chat. Your Dify chatflow collects name, phone number and the request, and asks for consent to call back.
- Create the contact.* Create Contact* adds the lead to your Famulor workspace. If the contact already exists, it is merged instead of duplicated.
- Start the call.* Start Outbound Call* gets your assistant's
assistant_idand the number in E.164 format, for example+4930123456. Pass context from the chat as JSON inVariables , such as{"customer_name": "Ada", "order_id": "A-1001"}. Your assistant knows right away what the call is about and doesn't have to ask everything again. - Read the result. A laterGet Call step reads the call's status, summary, analysis and transcript.
- Keep going. With that data, your workflow decides on the next step: update the CRM, send a follow-up or hand over to your team.
The benefit: chat and phone no longer run side by side. What was said in chat flows into the call, and what happened on the call flows back into your workflow. If you also want to push call data out without polling, read our article on post-call webhooks.
More ideas for your workflows #
- Appointment confirmation after a form: Someone fills out a form, your workflow creates the contact and an assistant calls to confirm.
- Callback after a support chat: When the chatbot can't solve an issue, it offers a callback instead of letting the conversation fizzle out.
- Start a campaign from your agent: UseList Campaigns to find the right campaign andStart Campaign to launch it, right from your Dify app.
- Review calls in chat: Ask your agent, for example, "Which assistants do I have?" or "Summarise my last 5 completed calls". It usesList Assistants ,List Calls andGet Call for that.
Setup in 4 steps #
- A Famulor workspace with API access. You need a workspace whose plan or add-on includes API access. No account yet?Sign up here.
- Create an API key. In Famulor, openSettings → API & MCP and create an API key. Copy it right away: it starts with
fam_and is shown only once. - Install the plugin in Dify. Install the plugin from theDify Marketplace , openTools → Famulor → Authorize and paste the key. When you save, the plugin checks your credentials with a read-only request.
- Check the Base URL. Leave the Base URL at
https://app.famulor.io. Only change it if you use Famulor under your ownwhite-label domain. Only HTTPS is accepted.
Tip: a key from the dashboard has full access to your workspace. If you want to limit permissions, you can create a key with narrower scopes through the API. The scopes each tool needs are listed in the plugin's README. You'll find all endpoints in the Famulor API reference, and a broader overview of API integrations in our article on API integrations for voice AI agents.
Use it responsibly #
Start Outbound Call and Start Campaign reach real people. Treat them differently from read-only tools:
- Only enable the call and campaign tools in agent apps when your users should actually be able to trigger calls.
- Make sure you have a lawful basis and, where required, consent for outbound calls in your country.
- Test new flows with your own number first before real leads get called.
The plugin never retries write actions such as starting a call, creating a contact or starting a campaign automatically. That way you avoid duplicate calls if a request fails.
Bonus: prefer n8n? #
If you'd rather build your automations in n8n, there's a community node, n8n-nodes-famulor, on npm.
Wrap-up #
The Famulor plugin gives your Dify agents a voice on the phone. Chat, call and analysis run in one workflow, with no exports and no switching tools. If you already use other assistant integrations, the plugin sits nicely next to our ChatGPT plugin.
Install the plugin from the Dify Marketplace and try the flow with your first assistant. Want to see how it fits your use case? Book a demo.
Writer at Famulor