woodennickel
Member
- Consent to Access & Modify
- I don't authorize Pabbly Support to log in to my account.
There is no action in Pabbly, for example, I want Pabbly, upon a trigger, to create a ticket in Moxie.
I added to the requests for integration some time ago, but its not available yet.
Zapier does have the create ticket action, so I figure its possible.
I got this from ChatGPT, and I am wondering if this makes sense... its a little beyond me, but I'll give it a try if it makes sense.
Yes — you can still create Moxie tickets from Pabbly Connect even without a pre-built “Create Ticket” action by using Pabbly’s API/HTTP request step to call Moxie’s Public API.
I added to the requests for integration some time ago, but its not available yet.
Zapier does have the create ticket action, so I figure its possible.
I got this from ChatGPT, and I am wondering if this makes sense... its a little beyond me, but I'll give it a try if it makes sense.
Yes — you can still create Moxie tickets from Pabbly Connect even without a pre-built “Create Ticket” action by using Pabbly’s API/HTTP request step to call Moxie’s Public API.
What you’ll use
- Moxie Public API has a Create Ticket endpoint: POST /action/tickets/create
- Your Moxie API Key is sent as a header named X-API-KEY, and you’ll use your workspace Base Endpoint URL
- In Pabbly, use API (Pabbly) / the API module to send a custom request
Step-by-step in Pabbly Connect (typical setup)
- In Moxie: enable API + copy Base URL + API Key
- Workspace settings → Connected Apps → Integrations → Enable Custom Integration (this shows your Base Endpoint URL + API Key)
- In Pabbly Connect: add an action
- Choose API (Pabbly) (or whatever Pabbly labels their API request module) → Execute API Request / similar.
- Configure the request
- Method: POST
- URL:
https://<your-moxie-base-host>/api/public/action/tickets/create
(Moxie docs show endpoints as “Base URL + /api/public/…”, and the ticket path is /action/tickets/create.) - Headers:
- Content-Type: application/json
- X-API-KEY: <your_moxie_api_key>
- Body (JSON): (map fields from previous Pabbly steps as needed)
{
"userEmail": "[email protected]",
"ticketType": "Fancy Support Request",
"subject": "Please do some work for me!",
"comment": "This is going to be a rad comment here.",
"dueDate": "2024-06-01",
"formData": {
"answers": [
{
"fieldKey": "ProjectType",
"question": "What type of project do you need?",
"answer": "Website design"
}
]
}
}
Common “gotchas” (so it actually works)
- userEmail must already exist as a known contact in your Moxie workspace or the ticket is rejected.
- If needed, you can add a prior Pabbly step that creates the contact first using Moxie’s “Create Contact” endpoint (listed in their Public API endpoints collection).
- ticketType must match exactly the Ticket Type name in Moxie (Tickets → Settings).
- Rate limit: Moxie notes a limit of 100 requests / 5 minutes for Public API.
