A development platform for building, shipping, and maintaining software with teams. Connect GitHub to Luffy to bring the supported parts of that workflow into a conversation. Start with the actions available in your connected account, then ask for a clear result in Slack or your linked WhatsApp conversation.
From your Slack workspace to WhatsApp
Discuss GitHub work with Luffy in Slack channels, threads, or direct messages. Link WhatsApp to your Luffy workspace to use connected tools and memory from your phone. You can ask for a quick answer or follow up on a task without setting up the connector again.
Slack is the shared team conversation; WhatsApp is another way to reach Luffy. Linking them does not mirror every message between the apps. Available actions, account permissions, and the audience for each result still matter.
How to connect GitHub with Luffy
- Open Luffy’s connector settings, find GitHub, and complete the connection requirements shown there. Select the account your team intends to use and review its permissions.
- Ask Luffy which GitHub actions are available. Try a small request with a known item, link, or input and compare the result with the source application.
- Use Slack for a shared team discussion. To work from your phone, link WhatsApp to your Luffy workspace using the platform settings; connecting a tool alone does not link your WhatsApp identity.
- Specify the result you want, who should receive it, and which changes require your approval. Verify one GitHub task before making it a recurring workflow.
Benefits for your team
Less switching between tools
Describe the GitHub task to Luffy in Slack or linked WhatsApp. Keep the request and explanation together instead of copying instructions between apps.
A result your team can use
Ask for a short answer, a reviewable draft, or a structured output from the available GitHub actions. Include source references where the tool returns them.
Connected work on your phone
Linked WhatsApp gives you access to Luffy’s connected tools and memory away from your desk. Ask for the GitHub context you need without configuring a separate automation for each messaging app.
Use cases
Prepare a pull request review brief
Provide the repository and pull request link. Ask Luffy to summarize the accessible change, checks, and open review questions with GitHub, where the connected tools support it. Expected output: a review brief with file references and unresolved risks. Benefit: Help reviewers understand the change before deciding whether to approve it.
Check what is possible before starting
Ask: “Which GitHub actions are available to me? I want to work on issues, deployments, incidents, code, and operational signals. Explain the required inputs and tell me if this connector cannot do the task.” Benefit: choose a supported workflow before spending time on setup.
Turn one task into a clear deliverable
Ask: “Use GitHub for this task: [describe the job]. Use [specific input or record], return [desired output], and flag missing information. Draft any changes for review first.” Benefit: a precise brief and an output you can check, with fewer handoffs.
Prepare a team handoff
After a task, ask: “Summarize what you completed with GitHub, what remains blocked, and what needs my decision. Prepare a short update for the team.” Use Slack for the shared discussion or linked WhatsApp for a personal follow-up. Benefit: the team gets the outcome and next steps without reconstructing the conversation.
GitHub connector FAQ
What can Luffy do with GitHub?
The available actions depend on the connector implementation, the connected account, and its permissions. Check the actions in your workspace before relying on a read, write, export, or scheduled task. A provider’s general product features are not automatically all exposed through its connector.
Can I use GitHub from both Slack and WhatsApp?
Luffy supports Slack and linked WhatsApp as conversation channels with access to connected tools and memory. Connect GitHub in your workspace and link WhatsApp separately.
Does connecting GitHub automate everything immediately?
No. Start with a specific request and verify its result. For recurring work, define the schedule, scope, destination, and approval requirements. Provider quotas, subscriptions, and available actions still apply.
How should we handle sensitive information and changes?
Choose the appropriate account and audience for GitHub results. Review proposed edits or outgoing messages before authorizing them, and check the source application to confirm completion. Connecting a tool does not make its data appropriate for every conversation.
