All connectors
Implemented
IoT & connected devices

Particle

Read authorised Particle IoT devices and connectivity status without invoking hardware functions.

Read authorised Particle IoT devices and connectivity status without invoking hardware functions.

Source actions

1

Destination actions

0

Data types

1

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

devices
  • List authorised devices
    Source

    Devices visible to the authenticated Particle user.

    devices.list

Authentication

Provider-issued access token

Plans and access

Provider account and API access with permission for the documented read operation. Account, country and product eligibility are determined by the provider; no universal regional availability is claimed.

Test environment

No credential-backed sandbox run has been recorded. Use an approved test account before production acceptance.

Rate limits

Provider account quotas apply; HTTP 429 uses bounded retries and Retry-After when supplied.

Pagination

User device listing is an unpaginated array; product-fleet pagination is not included.

Provider events

Not included in this read-only batch. Nexra event triggers are not yet available; flows run on demand or on a schedule.

Before you build a flow

  • Fixture-tested implementation only; provider sandbox and authorised-account validation have not run.
  • Only the listed reads are implemented. Writes, consent flows and automatic access-token refresh are not included.

Developer reference

  1. Create the Particle credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose Particle, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide

Machine-readable detail: GET /api/public/connect/connectors/particle and the Connections API.