Connect your workspace
1
Make an API key
In Wiredesk, go to Developers → API keys and make a key for Pipedream. Only owners and admins see the Developers section. Choose Read only if the workflows only read. The instant triggers need Full access, because they add a webhook endpoint. See Authentication.
2
Connect the account
In a Pipedream workflow, add a Wiredesk trigger or action, click Connect Account, and paste the key.
Actions
Send Message works as described in Talk to an agent. Pass back the
conversation_id from the first reply to continue the conversation. Set User ID to your own ID for the person, so their conversations share one contact.
Triggers
New Conversation Started checks for new items on a schedule, because Wiredesk sends no event when a conversation starts. It fires before the conversation has a summary. Use Conversation Ended to get the summary.
How instant triggers work
- Deploying an instant trigger adds a webhook endpoint in Wiredesk for the trigger’s URL. You’ll see it under Developers → Webhooks, described as
Pipedream: <event>. Deleting the trigger removes the endpoint. Changing its settings removes it and adds a new one. - Adding the endpoint takes a Full access key.
- A workspace can have up to 10 webhook endpoints, and each instant trigger that’s on uses one. If you’ve reached 10, delete a trigger you no longer need or remove an endpoint you don’t use.
- Every delivery is signed. The trigger checks the signature with the endpoint’s secret, which it keeps in its own storage, and answers
401to a request that doesn’t match or is more than five minutes old. Nothing is emitted for it. - New Lead Captured and Conversation Ended emit up to 10 recent items when they’re deployed, so you have real events to build the workflow with.
- Phone and browser-voice lines aren’t sent as New Message events. Use Conversation Ended, then Get Conversation with the transcript, to read them.
Errors
A failed step shows the API’s error code and message.unauthorized means the key is wrong, revoked, or its maker is no longer an owner or admin. read_only_key means a change was tried with a Read only key. Every request is in Developers → Logs, under the key’s name. See Request logs and Conventions for the rest.