Home Apps and Integrations
🕹️

Apps and Integrations

Supercharge Akece by linking it with your favorite tools and apps for a seamless workflow.
StĂŞnio AnĂ­bal
By StĂŞnio AnĂ­bal
• 4 articles

How to Use Webhooks in Akece

Webhooks allow you to integrate Akece with external platforms and systems. Whenever a specific action occurs — such as a new message being sent or a conversation being created — a webhook can be triggered automatically, sending the relevant data in real time to a URL you define. You can create multiple webhooks in the same account, each with different destinations and monitored events. How to Add a Webhook Step 1 – Access the Settings Go to Settings → Integrations → Webhooks Click the Configure button. Step 2 – Create a New Webhook Click Add new webhook. - Enter the URL that should receive the POST requests. - Select the events you want to monitor. Only the selected events will trigger requests. Akece will send a POST request with a JSON payload whenever one of the selected events occurs. Example of a Message Payload { "event": "message_created", "id": "1", "content": "Hi", "created_at": "2024-04-07 10:00:00 UTC", "message_type": "incoming", "content_type": "text", "content_attributes": {}, "sender": { "id": "1", "name": "Agent", "email": "[email protected]" }, "contact": { "id": "2", "name": "JoĂŁo Silva" }, "conversation": { "display_id": "1234", "additional_attributes": { "browser": { "device_name": "iPhone", "browser_name": "Safari", "platform_name": "iOS", "browser_version": "15.4", "platform_version": "15" }, "referer": "https://mysite.com" } }, "account": { "id": "1", "name": "My Company" } } Available Events You can choose from the following events when configuring a webhook in Akece: - conversation_created Triggered when a new conversation is started. - conversation_updated Triggered when any attribute of a conversation is updated. - conversation_status_changed Triggered when a conversation's status changes (e.g., from "open" to "resolved"). - message_created Triggered when a new message is sent in a conversation. - message_updated Triggered when an existing message is edited. - webwidget_triggered Triggered when a visitor opens the chat widget on your website. Each event sends a payload with specific data related to the type of action and the involved objects (such as contact, agent, conversation, message, etc.). Payload Structure The main objects that may be included in the webhook payloads are: - Account - Inbox - Contact - User (agent) - Conversation - Message Each object contains its own set of attributes — such as id, name, email, status, and others — to help you accurately identify and process the data. With Akece webhooks, you can automate tasks, sync data with external systems in real time, and create powerful custom workflows for your business. If you need help setting up or using webhooks, get in touch with our team: đź“© [email protected] | 📱 @akece.ai Next step: explore Akece’s API to expand your integrations even further!

Last updated on Apr 16, 2025

How to Translate Messages with Google Translate

If you or your team receive messages in unfamiliar languages, you can activate the Google Translate integration to translate messages directly within the Akece dashboard. This helps you communicate with customers in different languages without leaving the conversation. How to Enable the Google Translate Integration 1. Go to Settings → Apps → Google Translate 2. Click the Configure button 3. On the app page, click Connect 4. Enter your Google Cloud Project ID and Service Account Key File Need help? Follow this Google guide to obtain your credentials. 5. Click Create to complete the integration âś… Google Translate is now active in your Akece account. How to Set the Translation Language Translations are based on the default site language. To change it: 1. Go to Settings → Account Settings 2. In the Site Language field, select your preferred language 3. Click Update settings at the top right 👉 Agents can also set their own personal language preferences in their Personal Settings. How to Translate a Message When you receive a message in an unfamiliar language: 1. Click the three-dot icon next to the message 2. Select Translate 3. The translation will appear directly below the original message This allows you to understand and respond without switching tabs or tools. How to Create a Google Cloud Service Account To use Google Translate, you must create a service account and generate an authentication key: 1. Go to the Google Cloud Console 2. Create or select a project 3. Go to APIs & Services → Library 4. Search for Cloud Translation API and click Enable 5. Enable billing if it’s not yet active 6. Go to IAM & Admin → Service Accounts 7. Click Create Service Account - Give it a name (e.g., translate-api-user) - Assign the role Cloud Translation API User 8. After creation, go to the Keys tab - Click Add Key → Create new key (JSON format) - Download and securely store the JSON file Use the contents of this file in the Service Account Key File field when setting up the integration in Akece. If you need help enabling the Google Translate integration or configuring your Google Cloud project, reach out to us: đź“© [email protected] | 📱 @akece.ai

Last updated on Apr 16, 2025

How to Integrate Your Dialogflow Chatbot with Akece

Chatbots are great allies for support teams. They help handle repetitive questions, freeing up agents to focus on more strategic and complex conversations. Akece allows you to integrate your Dialogflow chatbot — one of the most popular NLP (Natural Language Processing) platforms — in just a few minutes. This guide explains how to create a bot in Dialogflow and connect it to Akece. Creating a Bot in Dialogflow 1. Access the Dialogflow Console. 2. Click Create Agent. 3. Enter the agent’s name, language, and time zone. Then click Create. Dialogflow will automatically create two default intents: - Default Welcome Intent - Default Fallback Intent You can add new intents to handle different flows and topics in your bot. đź’ˇ Tip: Akece also supports advanced intents, like handoff to human agents and interactive messages. See examples below. Creating a Google Cloud Service Account To connect Dialogflow to Akece, you need to generate a service account: 1. In Dialogflow, click the Project ID at the top to open Google Cloud Console. 2. Go to IAM & Admin → Service Accounts. 3. Click Create Service Account. 4. Enter a name and description, then click Create and Continue. 5. Assign the role Dialogflow API Client, then click Done. 6. Open the newly created service account. 7. Go to the Keys tab → Add Key → Create New Key (JSON). 8. Download the file and store it safely — you'll need it for the next step. Connecting Dialogflow to Akece 1. Go to Settings → Apps → Dialogflow, then click Configure. 2. Click Add new hook. 3. Fill in the form with: - Project ID (found at the top of the Google Cloud Console) - Service Account Key File (paste the full JSON content) - Inbox where the bot will be active 4. Click Save — and you’re done! Your bot is now integrated with Akece. Advanced Intents Handoff to a Human Agent To let a human take over the conversation, configure a handoff intent in Dialogflow: 1. Create an intent named "Handoff Intent" (or similar) 2. Add training phrases like: - “I want to talk to a person” - “I need human help” 3. In Responses → Custom Payload, add: { "action": "handoff" } This payload tells Akece to change the conversation status to open and assign it to a human agent. Interactive Messages 📝 Available only for website inboxes. You can create intents that return cards, lists, or article recommendations. Example using a select list: { "content_type": "input_select", "content": "Choose your favorite dish:", "content_attributes": { "items": [ { "title": "Sushi", "value": "I like sushi" }, { "title": "Pizza", "value": "I like pizza" }, { "title": "Biryani", "value": "I like biryani" } ] }, "private": false } When the user clicks an option, the value is sent back to Dialogflow. You can use it to trigger follow-up intents. Can Agents Return the Conversation to the Bot? Yes. When a bot is connected to an inbox, conversations start with Pending status — meaning the bot is in control. Once a handoff happens, the status changes to Open, and the bot stops responding. If the agent wants the bot to take over again, they just need to change the conversation status back to Pending. Need help connecting your chatbot to Akece? Contact our support team: đź“© [email protected] | 📱 @akece.ai

Last updated on Apr 16, 2025

How to Use Dashboard Apps in Akece

Dashboard apps allow you to embed a custom application directly within the Akece interface. This feature is ideal for displaying information such as orders, billing history, or customer data right next to the conversation — making your support team's job faster and more efficient. Your application will load inside the Akece interface and will automatically receive the contact and conversation context via browser events. How to Create a Dashboard App 1. Go to Settings → Integrations → Dashboard Apps. 2. Click the Configure button under Dashboard Apps. 3. Fill in the following fields: - App name: internal name for identifying your app. - App URL: the URL where your application is hosted. Once saved, a new tab will appear in the conversation sidebar with the app name. When clicked, your application will load inside Akece and receive context information automatically. How to Receive Data from Akece Akece sends the contact and conversation context using a browser message event. You can capture this data in your app with a simple event listener: window.addEventListener("message", function (event) { if (!isJSONValid(event.data)) return; const eventData = JSON.parse(event.data); // Use eventData as needed }); How to Request Context on Demand If you prefer to manually request the context data, you can send a message to the parent window: window.parent.postMessage('akece-dashboard-app:fetch-info', '*'); Akece will respond with the context of the conversation, contact, and logged-in agent in the following format: Example Payload { "event": "appContext", "data": { "conversation": { // Conversation details: messages, status, tags, custom attributes, etc. }, "contact": { // Contact info: name, email, phone, custom attributes, etc. }, "currentAgent": { // Logged-in agent info } } } Payload Fields Overview conversation: - Conversation ID, status, tags, timestamps - List of messages with sender, type, and content - Browser attributes and referrer - Agent and inbox info contact: - Name, email, phone, custom attributes - Social profiles (if available) - Last activity currentAgent: - Name, email, and ID of the currently logged-in agent With this setup, your application is now fully integrated with the Akece dashboard — with real-time access to relevant customer data. This is a powerful way to extend your support workflows by embedding apps that show order history, subscription details, past payments, and much more — all within the same view. Need help setting up your custom app in Akece? Reach out to our support team: đź“© [email protected] | 📱 @akece.ai

Last updated on Apr 16, 2025