# Particle

### Overview

Qubitro offers a no-code integration with Particle Cloud, enabling automatic synchronization of your Particle devices and telemetry data directly into your Qubitro projects.

* Devices from Particle Cloud are automatically created in Qubitro.
* Telemetry data flows seamlessly without manual forwarding setup.

### Prerequisites

* [x] Administrative access to both Particle Cloud and Qubitro.
* [x] A Qubitro account with an existing project.
* [x] A Particle account with active devices.
* [x] A data must be a valid key-value JSON object.

### How It Works

When Particle Cloud devices send telemetry events, Qubitro automatically receives and processes data without requiring additional device-side configuration.

### Creating the Integration

{% stepper %}
{% step %}
**Create an Integration in Qubitro**

* Log in to the [Qubitro Portal](https://portal.qubitro.com).
* Choose a project from the list.
* Click **New Source** and select **Particle** from the available sources.

<figure><img src="/files/enqzGz2dfv5dOu59AlDp" alt="" width="563"><figcaption><p>Qubitro Particle Integration Credentials</p></figcaption></figure>

* Keep this page open to use in the next step.
  {% endstep %}

{% step %}
**Configure Webhook on Particle Console**

Log in to your Particle Console and configure the webhook:

* Click **Integrations** from the left navigation menu.
* Click **New Integration** and select **Webhook**.
* Fill in the following fields:

<table><thead><tr><th width="267.16015625">Field</th><th>Value</th></tr></thead><tbody><tr><td><strong>URL</strong></td><td><code>https://webhook.qubitro.com/integrations/particle</code></td></tr><tr><td><strong>Request Format</strong></td><td>JSON</td></tr><tr><td><strong>Request Type</strong></td><td>POST</td></tr><tr><td><strong>Device</strong></td><td>Any</td></tr></tbody></table>

**Example Configuration:**

<figure><img src="/files/DHBvZ51xkkhzvNUbOyCU" alt=""><figcaption></figcaption></figure>

* Under **Extra** Settings, **leave** JSON DATA as is:

```json
{
  "event": "{{{PARTICLE_EVENT_NAME}}}",
  "data": "{{{PARTICLE_EVENT_VALUE}}}",
  "coreid": "{{{PARTICLE_DEVICE_ID}}}",
  "published_at": "{{{PARTICLE_PUBLISHED_AT}}}"
}
```

<figure><img src="/files/QGQH4tKTHzjiDRCMfJCW" alt=""><figcaption></figcaption></figure>

* Under **Extra Settings** and in the **HTTP Headers** section, add:

| Header Name           | Header Value                               |
| --------------------- | ------------------------------------------ |
| **projectId**         | `<PROJECT_ID>` (copy from Qubitro)         |
| **webhookSigningKey** | `<WEBHOOK_SIGNING_KEY>`(copy from Qubitro) |

**Example Configuration:**

<figure><img src="/files/31wIJuogEBGYLuXRtouQ" alt=""><figcaption></figcaption></figure>

* Click **Create Webhook**.
  {% endstep %}

{% step %}
**Verify the Integration**

* Return to the Qubitro Portal.
* Click **Go to project** and then **Refresh** to confirm that devices are listed successfully.

<figure><img src="/files/A5jwOBGxysERS1EOyZ2I" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

### FAQs

<details>

<summary>Do I need additional forwarding configuration in Particle Cloud?</summary>

No. The integration directly connects Particle Cloud and Qubitro without additional setup.

</details>

<details>

<summary>Are there additional costs for this integration?</summary>

No. There are no hidden costs or additional fees for data transfer or using the Qubitro <> Particle integration.

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.qubitro.com/data-sources/no-code-integrations/particle.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.