Integrations
Jigward works where your team already works.
Connect the tools once; then give Jigward work in them and read the result there. Anything with an HTTP API connects as a custom integration.
6 available, 3 coming soon
-
GitHub
Source control
Draft pull requests on a branch of their own, reviews when asked, and answers to review comments.
-
Slack
Team chat
Answers a mention in its thread, reading the messages before it, and takes work on as a Task there.
-
Jira
Issue tracking
An issue assigned to Jigward becomes a Task, and the issue's status follows the work.
-
AWS CloudWatch Logs
Observability
Tasks and private Chats search and query the log groups an admin allows, with no AWS credential kept.
-
Browser
Testing
Opens your app in a real browser and signs in with a profile; Jigward types the values itself.
-
Custom API
Your own APIs
Describe any HTTP API. Jigward drafts its operations from the public documentation, and an admin applies them.
-
Microsoft Teams
Team chat Coming soon
Listed as coming soon in Jigward's integrations.
-
Telegram
Team chat Coming soon
Listed as coming soon in Jigward's integrations.
-
GitLab
Source control Coming soon
Listed as coming soon in Jigward's integrations.
Nothing matches that. If it has an HTTP API, Jigward can connect it as a custom integration.
Product names are trademarks of their owners, and naming them does not mean they endorse Jigward. GitHub and the Invertocat logo are trademarks of GitHub, Inc. Slack and the Slack logo are trademarks of Slack Technologies, LLC. Telegram and the Telegram logo are trademarks of Telegram; Jigward does not represent Telegram.