This article covers the most common errors when automating Kixie action steps in HubSpot Workflows, and what each one means.
To find these errors in your workflow, go to the Action Logs page by clicking View > Action Logs.
In the Action Logs, the Event column shows whether each action failed or succeeded.
The first thing to check is whether the error says "Action Failed" or "The connected app returned an error". The difference tells you where the problem is:
- Action Failed means the error is coming from HubSpot.
- The connected app returned an error means the error is coming from Kixie's server. Hover over the Contact and click Event Details for the specific message.
Kixie: Send an SMS
"Action Failed"
The error is coming from HubSpot. Check the fields in the Action Step itself: Number to SMS, Message and owner.
Possible reasons for failure:
- The Contact does not have a phone number in the selected field
- The Contact does not have a Contact Owner
"The connected app returned an error"
The error is coming from Kixie's server. Click Event Details to read it.
-
"Invalid Accountid or Owner" — usually means the sender of the Auto-SMS is not a Kixie user, or that user has not integrated HubSpot into their dialer.
- Either change the Contact Owner of the enrolled Contact, or have the existing Contact Owner connect HubSpot to Kixie.
- If that owner was already connected, have them remove the integration and add it back. See HubSpot Says "Email Was Not Found at HubSpot" for the reconnect steps.
-
"Invalid Request" — usually means too many requests hit the Kixie servers at once.
- Limit how many contacts are enrolled at once. Segment them into batches of no more than 100.
- Note: this error is an initial response from the server. Kixie retries the action, so there is a good chance the SMS did eventually send. Check the SMS History page in the Kixie Dashboard before resending, so you do not send twice.
Kixie: Add Contact to PowerList
"Action Failed"
The error is coming from HubSpot. Check the PowerList Id and Number to Target fields, which are the only two required for this action.
Possible reasons for failure:
- The PowerList Id is incorrect. Confirm it against the PowerList in the Kixie Dashboard.
- The Number to Target is empty for that contact. If the action uses the Mobile Phone Number field, the enrolled Contact needs a number in that specific field.
"The connected app returned an error"
The error is coming from Kixie's server. Click Event Details to read it.
-
"Invalid Request" — again usually too many requests at once.
- Enrol in batches of no more than 100. For larger volumes, use CSV Upload or HubSpot List Ingestion instead, described in CRM Lists: How to Import a HubSpot CRM List.
- Note: Kixie retries the action, so the contact may well have been added. Check the PowerList Contacts page in the Kixie Dashboard before retrying.
If an error persists after these checks, contact support@kixie.com with your business ID and a screenshot of the Event Details.
Was this article helpful?
Articles in this section
- Kixie's HubSpot Integration: Configuration and Behavior
- HubSpot Says "Email Was Not Found at HubSpot"
- Managing MaestroAI HubSpot Workflows
- How to Disconnect Your Kixie Integration from HubSpot
- How to Disconnect Your HubSpot Integration from Kixie
- HubSpot Workflows: How to Troubleshoot Common Errors
- CRM Lists: How to Import a HubSpot CRM List
- HubSpot Workflows: Maintain Your Kixie PowerList via HubSpot Workflows
- HubSpot Workflows: Using a Recent Incoming Call to Trigger or Stop a HubSpot Workflow
- HubSpot Workflows: Using a Recent Incoming SMS to Trigger or Stop a HubSpot Workflow