Manifst Connectors

Connect Manifst to your software development tools to automatically synchronize tickets with your Git activity and receive real-time notifications in Slack and Discord.

Overview

Connectors are configured per project under Settings → Integrations. Only project owners can create or edit connectors.

Who gets access

A subscription grants capabilities to the account, never to the project. Being invited to a paying subscriber's project therefore grants no rights over their connectors: every member is assessed on their own plan.

Their work still feeds the connectors, though: their commits are linked to tickets, their edits are pushed to Jira, their actions fire notifications. The subscriber paid for a complete view of their project's delivery : a teammate's contribution is not removed from it, it simply stays invisible to that teammate.

GitHub

Configuration

1. In Manifst, open Settings → Integrations → GitHub → Configure.
2. Copy the displayed secret key (visible only once).
3. In GitHub, open your repository → Settings → Webhooks → Add webhook.
4. Payload URL: the URL displayed in Manifst after saving.
5. Content type: application/json required
6. Secret: the secret key copied in step 2.
7. Events: Pushes + Pull requests.
8. Click Add webhook. GitHub sends a ping event : Manifst responds {"ok":true}.

Push : Link a commit to a ticket

Include a #<PREFIX>-<id> reference in your commit message to automatically link the commit to the matching item.

#<PREFIX>-<numeric id>

The prefix is the one shown in front of the item in Manifst. Every ticket type defined in the project is recognised : not just US : along with both roadmap levels:

git commit -m "fix: login form validation #US-42"

git commit -m "feat: add pagination support #US-17 #US-18"

git commit -m "fix: crash on startup #BG-7"

Multiple references in a single commit are supported.

Branch name

The branch name is parsed too, without the hash sign: no commit-message discipline is needed when your naming convention already carries the reference.

git checkout -b feature/US-42-login-form
git checkout -b hotfix/BG-7

The branch then appears in the Development panel of the item, next to commits and pull requests.

Pull Requests

Mention one or more items in the PR title or description, using the same syntax as for commits. The PR's source branch is parsed as well: a PR coming from feature/US-42-… is linked even without an explicit mention.

GitHub's closing keywords (fix, fixes, close, closes, resolve, resolves…) placed in front of a reference are recognised and recorded as a closing intent.

## Changes
User profile form implementation.

Closes #US-15 #US-23

The link status in Manifst is updated automatically whenever the PR state changes:

Auto-close stories on merge

When a PR is merged, Manifst can automatically move linked tickets to a designated "Done" column.

To enable this feature:

1. In Settings → Integrations → GitHub, toggle on Automatically close stories on merge.
2. Select the destination column from the dropdown list (columns of type "done" in your Kanban board).
3. Save. Any merged PR referencing a ticket will move the referenced tickets to that column, whatever their prefix.

Once, at merge time

Closing fires on the event that performs the merge, not on the "merged" state. In practice, if you reopen a ticket by hand afterwards, later editing the PR title or description will not close it again. A human decision is never overwritten by a text change on GitHub.

An automatically closed ticket carries an "auto-closed" note under the matching link, in the Development panel of its page.

GitLab

Configuration

1. In Manifst, open Settings → Integrations → GitLab → Configure.
2. Copy the displayed token (visible only once).
3. In GitLab, open your project → Settings → Webhooks → Add new webhook.
4. URL: the one displayed in Manifst after saving.
5. Secret token: the token copied in step 2.
6. Trigger: Push events + Merge request events.
7. Leave Enable SSL verification ticked, then Add webhook.

References

The syntax is identical to GitHub: #<PREFIX>-<id> in a commit message, the branch name parsed without a hash sign, and closing keywords recognised. See the GitHub section for details : it is literally the same parsing code.

Private repositories and self-managed instances

The connector is inbound: GitLab calls Manifst. A private repository therefore works exactly like a public one : no repository access token is needed, and Manifst never reads your code.

A self-managed instance works too, on one condition: it must be able to reach Manifst's public URL. An instance behind a corporate firewall can often call out even when inbound access is impossible : what matters is the direction of travel.

One nuance about links: the ones recorded point at your repository. On a private repository, a Manifst member without GitLab access will land on a login page. That is the expected behaviour : repository permissions belong to GitLab.

Azure DevOps

The same linking as GitHub and GitLab, applied to Azure Repos Service Hooks. The parsing engine is the same code: reference syntax does not change from one platform to the next.

Setup

Azure DevOps does not create one webhook covering several events: it creates one subscription per event. You therefore repeat the operation, pointing at the same URL, for each event type you want to track.

1. In Manifst, open Settings → Integrations → Git connector → Configure, pick Azure DevOps, fill in the repository URL and save.
2. Copy the token and the webhook URL shown (the token is displayed only once).
3. In Azure DevOps, open Project settings → Service hooks, then Create subscription.
4. Service: Web Hooks. Trigger: Code pushed.
5. On the Action screen: paste the Manifst URL into URL, and under HTTP headers enter the line:
   X-Manifst-Token: <your token>
6. Leave Resource details to send on All.
7. Test, then Finish.
8. Repeat steps 3 to 7 for Pull request created, Pull request updated and Pull request merge attempted.

References

The syntax is identical to GitHub: #<PREFIX>-<id> in a commit message or a pull request description, the branch name parsed without the hash, and the same closing verbs. See the GitHub section for details.

Private repositories and Azure DevOps Server

The connector is inbound: Azure calls Manifst. A private repository therefore works exactly like a public one : no repository access token is needed, and Manifst never reads your code.

An Azure DevOps Server (self-hosted) instance works too, provided it can reach Manifst's public URL. What matters is the direction of travel: an instance behind a corporate firewall can often call out even when inbound access is impossible.

Linear

Sync a Linear team with Manifst bidirectionally: Initiatives, Projects, Issues, sub-issues, Cycles, comments, labels/tags, estimates, and dependencies.

Setup

1. In Linear, open Settings → Account → API (or Workspace → API) and generate a Personal API Key.
2. In Manifst, go to Settings → Integrations → Backlog connector → Configure, then pick Linear.
3. Connection : paste your Linear API Key and click Test. Manifst validates the key and lists all accessible teams in your workspace.
4. Team & Prefix : select the Linear Team to sync. You can set a prefix for ticket types (default Type /, e.g. labels named Type / Bug become the Bug ticket type in Manifst).
5. Frequency : adjust the automatic background sync interval (from 5 to 1440 minutes, 10 min by default).
6. Sync : Manifst reads the Linear backlog, calculates the diff (creations, updates), and only writes to Manifst once you click Save to Manifst.

Mapping

Dependencies between tickets

Linear supports multiple relation types between issues (blocks, duplicate, related). Manifst filters and synchronizes only blocks relations ("blocks" / "is blocked by"), as they are the only ones defining strict execution order.

Limits & Best Practices

• Single Team Scope: Each Linear connector is bound to a single team in your Linear workspace. To sync multiple teams, configure the connector on respective Manifst projects.
• Matching Email Addresses: Automatic assignment of tickets and comment authorship require members to use identical email addresses in both Linear and Manifst.
• Markdown ↔ HTML Conversion: HTML descriptions and comments written in Manifst are converted to Markdown for Linear, and vice-versa.

Bitbucket

Setup

1. In Manifst, open Settings → Integrations → Git connector → Configure, pick Bitbucket, fill in the repository URL and save.
2. Copy the secret and the webhook URL shown (the secret is displayed only once).
3. In Bitbucket, open your repository → Repository settings → Webhooks → Add webhook.
4. Title: "Manifst". URL: paste the Manifst URL.
5. Secret: paste the Manifst secret. This field is optional for Bitbucket, but mandatory for Manifst : see the warning below.
6. Triggers: tick Repository → Push, then, under Pull request, tick Created, Updated, Merged and Declined.
7. Leave Status on Active, then Save.

References

The syntax is identical to GitHub: #<PREFIX>-<id> in a commit message or in a pull request description, the branch name parsed without the hash sign, and the closing verbs recognised. See the GitHub section for details.

Private repositories

The connector is inbound: Bitbucket calls Manifst. A private repository therefore works exactly like a public one : no repository access token is needed, and Manifst never reads your code.

The only nuance concerns links: the ones recorded point at your repository. On a private repo, a Manifst member without Bitbucket access will land on a login page. That is the expected behaviour : repository permissions belong to Bitbucket.

Jira

Automatically sync your Jira Cloud backlog with Manifst (Tickets, Epics, Super Epics, and Story Points).

Setup

1. In Manifst, go to Settings → Integrations → Backlog connector → Configure, then pick Jira.
2. Connection : enter your Jira site URL (e.g. https://your-site.atlassian.net), your Atlassian email and API token, then click Test.
3. Project : specify the project key (e.g. PROJ).
4. Mapping : check the Jira types used for Epics and Super Epics, and the Story Points field.
5. Filter : adjust the JQL and the automatic sync frequency.
6. Sync : Manifst reads your backlog, shows what will change, and only writes once you click Save into Manifst.

Dependencies between tickets

Manifst only imports Jira links of type Blocks ("blocks" / "is blocked by"): they are the only ones that say which ticket comes first. A Relates, Duplicate or Cloners link carries no ordering and is ignored.

Azure Boards

Sync an Azure Boards project with Manifst, both ways: work items, hierarchy, iterations, comments, attachments and dependencies.

Setup

1. In Azure DevOps, create a personal access token: User settings → Personal access tokens → New Token, with the Work Items: Read, write & manage scope.
2. In Manifst, go to Settings → Integrations → Backlog connector → Configure, then pick Azure Boards.
3. Connection : enter your organization URL (https://dev.azure.com/my-organization) and the token, then click Test.
4. Project : pick the project and the team.
5. Mapping : Manifst detects the process template (Agile, Scrum, CMMI or Basic) and derives the four work item types. You can override them if your process is customized.
6. Filter : adjust the WIQL query and the automatic sync frequency.
7. Sync : Manifst reads the backlog, shows what will change, and only writes once you click Save into Manifst. Automatic sync then runs every 10 minutes by default.

Mapping

These types can be changed under advanced options in the modal if your process is customized.

Limits

• Azure DevOps Services only (the cloud). Self-hosted Azure DevOps Server is not supported.
• The Basic process only has three levels (Epic → Issue → Task): Manifst Super Epics are not pushed there.
• Deleting a Manifst ticket sends the work item to the Azure recycle bin, never a permanent destroy: it stays recoverable on the Azure side.
• Pruning items deleted on the Azure side only happens on a manual sync: automatic sync is incremental and cannot see what disappeared.

Slack

Configuration

1. In Slack, create an Incoming Webhook at api.slack.com/apps → your app → Incoming Webhooks → Add New Webhook to Workspace. Select the target channel.
2. Copy the generated Webhook URL (format: https://hooks.slack.com/services/T…/B…/…).
3. In Manifst, open Settings → Integrations → Slack → Configure.
4. Paste the URL into the Webhook URL field.
5. Check the desired events.
6. Click Test Connection to verify message delivery, then click Save.

Available Events

Message Format

Messages use Slack mrkdwn formatting. Here are examples for each event:

🔄 *Status updated* : *Update user profile*
Backlog → In progress

👤 *Story assigned* : *Add pagination*
Assigned to *Marie Dupont*

💬 *New comment* on *Update user profile*
By *Jean Martin*: Form must handle profile avatar upload…

🚀 *Sprint started* : *Sprint 3 : Auth & Profile*

✅ *Sprint ended* : *Sprint 3 : Auth & Profile*

Discord

Configuration

1. In Discord, open your channel → Channel Settings → Integrations → Webhooks → New Webhook.
2. Name the webhook (e.g. Manifst), select the channel, then click Copy Webhook URL.
   The URL format is https://discord.com/api/webhooks/<id>/<token>.
3. In Manifst, open Settings → Integrations → Discord → Configure.
4. Paste the URL into the Webhook URL field.
5. Check the desired events.
6. Click Test to send a test message to Discord, then click Save.

Available Events

Events are identical to the Slack connector : a single event can trigger both Slack and Discord webhooks simultaneously if both are enabled.

Embed Format

Discord notifications utilize embeds with distinct sidebar colors per event type. Text supports standard Discord Markdown (**bold**, *italic*, `code`).

Sample Discord webhook JSON payload:

{
  "embeds": [{
    "description": "🔄 **Story updated** : **Update user profile**\nStatus: `Backlog` → `In progress`",
    "color": 5793266
  }]
}

Google Meet

Turn your Google Meet meeting recordings and transcripts into Epics, User Stories, and subtasks powered by Manifst AI.

Setup

1. In Manifst, go to Settings → Integrations → Google Meet → Connect.
2. Grant Manifst access to your Google Workspace meeting notes and transcripts via OAuth.
3. Once connected, click Meetings to view meetings with available transcripts.
4. Select a meeting and click Generate backlog: Manifst AI automatically structures your backlog items.

Power BI / REST API

This connector requires no configuration in Manifst : it consists of consuming the v1 API directly from Power BI. Refer to the API Documentation for the full list of endpoints.

Key & Prerequisites

• An account on the Portfolio plan (REST API access included).
• An API key generated under Settings → API Keys with at least finance:read (EVM & portfolio indicators) and roadmap:read (dependencies & milestones). Add tickets:read, time:read, team:read as needed.
• The Base API URL: https://manifst.net/api/v1

Before configuring Power BI, test your key with a quick PowerShell command : if it returns JSON {"data":[…]}, you are ready:

curl.exe -H "Authorization: Bearer mfst_live_YOUR_KEY" https://manifst.net/api/v1/projects

Connecting Power BI Desktop

The API authenticates via an Authorization: Bearer header. The most reliable pattern is declaring it inside a Power Query M script using Web.Contents (compatible with scheduled cloud refresh). Open Home → Transform data → New Source → Blank Query → Advanced Editor and paste:

let
    BaseUrl = "https://manifst.net/api/v1",
    ApiKey  = "mfst_live_YOUR_KEY",
    Source  = Json.Document(
        Web.Contents(BaseUrl, [
            RelativePath = "finance",
            Query   = [ project = "PROJECT_UUID" ],
            Headers = [ Authorization = "Bearer " & ApiKey ]
        ])
    )
in
    Source[data]

When Power BI prompts for authentication credentials, select Anonymous: credentials are passed directly via the HTTP header. Obtain your project UUID from the /projects endpoint.

Portfolio Roll-up (Multi-Project)

The /portfolio/finance endpoint aggregates EVM data for all accessible projects in a single request : perfect for program management. It returns a consolidated totals object plus project-level details.

let
    BaseUrl = "https://manifst.net/api/v1",
    ApiKey  = "mfst_live_YOUR_KEY",
    Source  = Json.Document(
        Web.Contents(BaseUrl, [
            RelativePath = "portfolio/finance",
            Headers = [ Authorization = "Bearer " & ApiKey ]
        ])
    ),
    Projects = Table.FromRecords(Source[data][projects])
in
    Projects

The consolidated roll-up block is accessible via Source[data][totals] (Σ BAC, portfolio CPI/SPI, total VAC…). To filter for specific projects, add Query = [ projects = "uuid1,uuid2" ].

Incremental Refresh & Pagination

Large endpoints /tickets and /time-entries support pagination and date filtering passed in the query parameters:

            RelativePath = "tickets",
            Query = [ project = "PROJECT_UUID", updated_since = "2026-07-01", per_page = "500", page = "1" ],
            Headers = [ Authorization = "Bearer " & ApiKey ]

let
    BaseUrl = "https://manifst.net/api/v1",
    ApiKey  = "mfst_live_YOUR_KEY",
    PerPage = 500,
    Page = (n as number) as record =>
        Json.Document(
            Web.Contents(BaseUrl, [
                RelativePath = "tickets",
                Query = [
                    project  = "PROJECT_UUID",
                    page     = Text.From(n),
                    per_page = Text.From(PerPage)
                ],
                Headers = [ Authorization = "Bearer " & ApiKey ]
            ])
        ),
    Pages = List.Generate(
        () => [ n = 1, r = Page(1) ],
        each List.Count([r][data]) > 0,
        each [ n = [n] + 1, r = Page([n] + 1) ],
        each [r][data]
    ),
    Tickets = Table.FromRecords(List.Combine(Pages)),
    // tags is a list of records : expand it or drop it
    Clean   = Table.RemoveColumns(Tickets, {"tags"}, MissingField.Ignore)
in
    Clean

Data Model

Every ticket carries the UUIDs of its project, epic and sprint. Those are the foreign keys of the model:

Remember to type the timestamps as well: they arrive in UTC as YYYY-MM-DD HH:MM:SS, and Power BI treats them as text until you convert them with Table.TransformColumnTypes.

Troubleshooting

Security

GitHub : HMAC Verification

GitHub requests are signed with HMAC-SHA256 via the X-Hub-Signature-256 header. Invalid signatures are rejected with HTTP 401.

Slack : SSRF Protection

Only https://hooks.slack.com/services/… endpoints are accepted. Webhooks pointing to local or private IP spaces are rejected.

Discord : SSRF Protection

Only https://discord.com/api/webhooks/<id>/<token> URLs are accepted. Tokens must match [A-Za-z0-9_-] patterns.

Rate Limiting

The Test Connection button is rate-limited to 5 calls per minute per user per project.

Slack & Discord Circuit Breaker

If delivery fails 5 consecutive times, the connector is automatically disabled to prevent silent errors. Re-enable it once the webhook URL is fixed.

FAQ

GitHub webhook returns ignored: invalid_json

Set GitHub webhook Content type to application/json in GitHub repository Settings → Webhooks.

Webhook returns ignored: integration_not_configured

The GitHub integration has not been created or was deleted for this project. Set it up in Settings → Integrations.

Commits are linked (refs_linked: 1) but story status does not change

A push links commits for reference without altering story status. To close stories automatically, use a merged Pull Request with auto-close enabled.

I am not receiving Slack notifications

• Verify event checkboxes in connector settings.
• Use Test Connection to ensure the Webhook URL remains valid.
• Check if the connector was disabled by the circuit breaker.
• Verify that the Slack app remains installed in your workspace.

Can I connect multiple GitHub repositories?

A single GitHub connector per project is supported. For multi-repo setups, configure multiple GitHub webhooks targeting the same Manifst URL.

A teammate cannot see the "Development" panel

Connectors are included from the Team plan onwards, and the capability is assessed on their subscription : not the project owner's, and not the project itself. A member on the Starter plan therefore sees neither the panel nor the commit badges, even on a project whose connector works fine. Their own commits are still linked, and remain visible to members who are entitled to them.

Lost GitHub secret key

Secrets are shown only once upon creation. If lost, click Regenerate Secret in Manifst and update the value in GitHub.

Not receiving Discord notifications

• Verify event checkboxes in connector settings.
• Use Test to verify webhook status.
• Check for circuit breaker auto-disablement.

Can Slack and Discord connectors be active simultaneously?

Yes. Both connectors function independently and send notifications simultaneously if configured for the same event.

Is the Discord token visible to non-owner project members?

No. Webhook URLs are masked in the API for non-owners (only the first 4 token characters are visible). Only project owners see the full URL.