Add Slack connector input targets and element template guidance#1
Open
bastiankoerber wants to merge 2 commits into
Open
Add Slack connector input targets and element template guidance#1bastiankoerber wants to merge 2 commits into
bastiankoerber wants to merge 2 commits into
Conversation
- Add exact Slack connector input targets (chat.postMessage, conversations.create, conversations.invite) to camunda-dev-guide.md - Document that data.messageType is required for chat.postMessage - Document correct field names (data.newChannelName not data.name, data.visibility not is_private) - Add element template warning: do NOT set zeebe:modelerTemplate attributes or elementTemplateId headers in generated BPMN XML — these cause "Template Not found" errors in Web Modeler - Update /new-process skill to reference element template JSON from the connectors repo for accurate input target discovery
- Expand "To configure any specific connector" section with step-by-step instructions for reading element template JSON (binding types, conditional properties, required fields) - Add comprehensive "Element Templates — do NOT set manually in BPMN XML" section explaining why zeebe:modelerTemplate attributes cause errors and how to correctly generate BPMN for Web Modeler compatibility - Add note that input target naming is connector-specific (REST uses flat names, Slack uses data.* prefix) — always check the element template - Update /new-agent skill with same element template guidance Validated against two connectors: - REST (io.camunda:http-json:1): flat targets, deployed and ran successfully - Slack (io.camunda:slack:1): data.* prefixed targets, learned correct field names through deployment error iteration
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
zeebe:modelerTemplateattributes cause "Template Not found" errors and the correct workflow for Web Modeler compatibilitychat.postMessage,conversations.create,conversations.invite) with correct field namesdata.*prefix)/new-processand/new-agentskills with element template guidanceContext
These learnings came from building and deploying processes via Claude Code to a Camunda 8 SaaS cluster. Key findings validated against two connectors:
data.newChannelNamenotdata.name,data.visibilitynotis_private)zeebe:modelerTemplatein BPMN XML doesn't work — the template must be applied through Web Modeler UI. Raw XML references don't link to the Modeler's internal catalogcamunda/connectorsrepo is the authoritative source — each property'sbindingobject maps directly tozeebe:inputtargets andzeebe:taskHeaderkeysTest plan
io.camunda:http-json:1): deployed and completed successfully with flat input targetsio.camunda:slack:1): deployed and completed successfully withdata.*prefixed targets