Quick Answer
Setting up an Acquire Kintone integration requires a third-party workflow automation platform like Zapier or Make because there is no native connection between the two systems. This integration empowers operations and support teams to automatically create a new Kintone database record for high-value customer support tickets closed in Acquire to track long-term account health. By bridging your customer engagement software with your custom database, you eliminate manual data entry and ensure critical support insights flow seamlessly into your internal tracking workflows.
Tool Comparison
| Feature / Detail | Acquire | Kintone |
|---|---|---|
| Category | Customer Support & Engagement | Workplace Collaboration & Database |
| Starting Price | $500 per month, billed annually (Base tier) | $24 per user/month, billed annually (Minimum 5 users) |
| Core Features | Omnichannel shared inbox, Co-browsing and screen sharing, AI-powered chatbots, Video and voice calls, Customer sentiment analytics | Custom relational databases, Automated workflow management, Built-in team communication, Role-based permission controls, Interactive graphical reports |
| Role in This Integration | Acts as the trigger source when a high-value customer support ticket is marked as closed. | Acts as the destination where a new database record is automatically generated for account health tracking. |
Why Connect Them
When your high-value enterprise clients submit inquiries, keeping their support records isolated from internal operational data creates dangerous blind spots. Bridging these platforms solves this by letting you automatically create a new Kintone database record for high-value customer support tickets closed in Acquire to track long-term account health.
Without this connection, account managers are forced to manually copy ticket details, resolution notes, and customer sentiment metrics across platforms. By establishing an automated bridge, every successfully resolved ticket for a key account instantly populates your custom Kintone database. This gives your entire organization immediate visibility into customer touchpoints and ongoing satisfaction trends without disrupting daily workflows.
Step-by-Step Setup Guide
Step 1: Prepare Your Workspace and Prerequisites
Before building your automated workflow, ensure you have active accounts for Acquire and Kintone, alongside a connected account in an automation platform like Zapier or Make. Confirm that you have administrative access to Kintone so you can configure database apps and fields, and verify that you have API or webhook access enabled in your Acquire environment.
Step 2: Establish the Trigger in Acquire
Log into your chosen automation platform (Zapier or Make) and create a new workflow. Set Acquire as your trigger application. Choose the event that signifies a resolved issue for a key account, such as "Ticket Closed" or an equivalent event tag indicating a high-value interaction. Authenticate your Acquire account using your credentials or API keys.
Step 3: Configure the Destination Action in Kintone
Add a second step to your workflow, selecting Zapier or Make's action module for Kintone. Select the action to create a new record. Authenticate your Kintone workspace and select the specific app and database space designated for account health tracking.
Step 4: Map Your Fields and Data
Map the data fields pulled from the closed Acquire support ticket to the corresponding fields inside your Kintone database record. Ensure that critical data points—such as customer name, ticket ID, resolution notes, and customer sentiment analytics—are accurately routed into your Kintone custom fields so your long-term tracking remains clean and reliable.
Step 5: Test and Go Live
Run a test payload using a recently closed ticket in Acquire to verify that the automation successfully formats and pushes the data into Kintone. Check your Kintone database to confirm the new record appears correctly with all mapped fields populated. Once verified, toggle your integration workflow from testing mode to live production.
Common Troubleshooting Issues
Zapier or Make cannot find my closed Acquire tickets
- Symptom: The automation builder fails to pull recent ticket data or throws an authentication error when connecting to Acquire.
- Likely Cause: Your user account lacks the necessary administrative permissions, or the API authentication token has expired.
- Fix: Regenerate your API credentials within Acquire, ensure your user profile has full access rights, and reconnect the account inside your automation builder.
New Kintone records are missing mapped text data
- Symptom: The integration creates a new record in Kintone, but fields like ticket descriptions or customer names appear blank.
- Likely Cause: Field data types in Kintone (such as single-line text versus multi-line text) do not match the data format sent by Acquire.
- Fix: Update your Kintone database field settings to match the data types coming from your automation platform or adjust your field mapping formulas.
Automation triggers on low-value tickets instead of high-value accounts
- Symptom: Every closed ticket in Acquire generates a record in Kintone, cluttering your long-term account health dashboard with noise.
- Likely Cause: The automation lacks a conditional filter step to separate standard tickets from high-value customer interactions.
- Fix: Insert a filter step immediately after your Acquire trigger in Zapier or Make to verify account tier or tag criteria before allowing the Kintone record creation action to run.
Integration errors out due to Kintone user permission limits
- Symptom: Workflow execution logs show a permission error or record rejection from the Kintone API.
- Likely Cause: The Kintone account used to authenticate the automation step lacks permission to add records to the specified database app.
- Fix: Log into Kintone, navigate to the specific app's settings, and ensure the user profile linked to the integration holds permission to create and edit records.
Frequently Asked Questions
Does Acquire integrate natively with Kintone?
No, there is no native integration between Acquire and Kintone. You must use a third-party workflow automation tool like Zapier or Make to connect the two platforms and transfer data.
What is the primary use case for connecting Acquire and Kintone?
The core use case is to automatically create a new Kintone database record for high-value customer support tickets closed in Acquire to track long-term account health. This eliminates manual data entry and keeps operational teams informed.
How much do Zapier or Make cost to run this integration?
Both automation platforms offer tiered pricing models, including limited free tiers and paid plans that scale based on the monthly volume of tasks or operations your workflows consume. You will need to check their respective pricing pages for current usage rates.
Can I filter which tickets trigger a new Kintone record?
Yes. By adding a filter step inside your Zapier or Make workflow, you can set rules based on Acquire tags, customer value tiers, or ticket categories so that only high-value interactions create Kintone database records.
Do I need developer resources to set up this integration?
No developer resources are required. Because platforms like Zapier and Make provide visual, no-code builders, operations and support team members can map fields and configure the integration independently.
What happens if the integration fails temporarily?
Most third-party automation tools automatically retry failed tasks for a set period or alert you via email if a workflow stops running. Once the underlying issue is resolved, you can typically replay the failed tasks from your automation history log.
Get Started with Your Tools
Ready to streamline your support and operational tracking? Start your trials today to build your custom workflows:
- Try Acquire
- Try Kintone
Disclosure: CoreStackGuide may earn a commission if you sign up through these links, at no extra cost to you.