# Bloomfire integrations: posts and questions

> Create a post, create a question and create an answer in Bloomfire, and start a workflow when Bloomfire sends “Post published”.

**Canonical page:** https://tray.ai/connectors/bloomfire-integrations/
**Categories:** Documents and e-signature
**Connects through:** HTTP Connector

## Overview

Bloomfire is a knowledge sharing platform where employees publish posts, ask and answer questions, group content into series, and search what their company knows. Tray.ai connects to Bloomfire through the HTTP Connector, so your workflows can call the Bloomfire API alongside the rest of your stack.

## Use cases

### Posts

Read, create, update, and delete posts in Bloomfire from any Tray.ai workflow. The Bloomfire API covers calls such as list posts and get a post.

- List posts
- Get a post
- Create a post

### Questions

Read, create, update, and delete questions in Bloomfire from any Tray.ai workflow. The Bloomfire API covers calls such as list questions and create a question.

- List questions
- Create a question
- Update a question

### Answers

Read and create answers in Bloomfire from any Tray.ai workflow. The Bloomfire API covers calls such as list answers to a question and create an answer.

- List answers to a question
- Create an answer
- Accept an answer

### Comments

Read, create, update, and delete comments in Bloomfire from any Tray.ai workflow. The Bloomfire API covers calls such as list comments and create a comment.

- List comments
- Create a comment
- Update a comment

### Users

Read, create, and update users in Bloomfire from any Tray.ai workflow. The Bloomfire API covers calls such as create or update a user and get a user.

- Create or update a user
- Get a user
- Update user data

### Webhook subscriptions

Read, create, update, and delete webhook subscriptions in Bloomfire from any Tray.ai workflow. The Bloomfire API covers calls such as list subscriptions and create a subscription.

- List subscriptions
- Create a subscription
- Update a subscription

## Challenges Tray.ai solves

### Keeping Bloomfire credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Bloomfire credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Bloomfire API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Bloomfire API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Bloomfire?

Yes. Tray.ai connects to Bloomfire through the HTTP Connector, which calls the Bloomfire API directly. Any call the Bloomfire API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Bloomfire?

The Bloomfire API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Bloomfire connector?

Bloomfire runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Bloomfire connector from the Bloomfire API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/