To access the Forms API, obtain an API key or set up OAuth credentials. Keep credentials secure and rotate regularly.
Authorize Adafruit IO with your Forms API connection using an API key or OAuth token. Restrict access to trusted apps and update permissions as needed.
– GET /forms/ — Retrieve a list of forms. – GET /forms/submissions — Retrieve submissions for a specific form. – API Endpoint3-17 — Placeholder for future endpoints.
Trigger: New form submission detected in the Forms API (GET /forms/submissions) triggers data push to Adafruit IO.
Actions: Map submission fields (submission_id, form_id, timestamp, data) to corresponding Adafruit IO feed fields and publish immediately.
Forms API method path: GET /forms/submissions; Adafruit IO publish uses its REST endpoint.
submission_id, form_id, timestamp, payload
Trigger: Daily or hourly pull of submissions via GET /forms/submissions with filters.
Actions: Append new submissions to an Adafruit IO feed; maintain idempotency with submission_id.
Forms API path: GET /forms/submissions; Adafruit IO ingest path.
submission_id, form_id, submitted_at
Trigger: Submissions that meet a threshold (e.g., value changes) create an event.
Actions: Update Adafruit IO dashboards with summary statistics; map fields to feed widgets.
Forms API: GET /forms/submissions; Adafruit IO: REST updates to feeds
submission_id, critical_value, timestamp
No expensive development or maintenance—set up automations with a few clicks.
Faster time-to-value with ready-made endpoints and triggers.
Easier data-driven IoT workflows without writing code.
Understand the core elements and processes used to connect APIs and apps: endpoints, triggers, actions, field mappings, and authentication.
A set of rules that allow one software program to interact with another.
A specific URL in an API that performs a function, such as GET /forms or POST /forms/submissions.
A user-defined callback URL that receives real-time data from another service when an event occurs.
An open standard for token-based authorization used by many APIs to grant scoped access.
Stream new form results directly into Adafruit IO dashboards to monitor trends in real time.
Trigger alerts in IoT devices or apps when specific form fields meet thresholds.
Archive submissions into Adafruit IO for long-term analytics and device state tracking.
Register your app and obtain an API key or OAuth token for the Forms API.
Map form fields to Adafruit IO feed fields to ensure data lands in the right place.
Run test submissions, verify in Adafruit IO, and enable the automation.
The Forms API provides access to form data and submissions without needing to modify your application code. It allows you to fetch forms and their submissions on demand. This is ideal for automations that react to new or updated form data in Adafruit IO.
Use an API key or OAuth credentials to secure the connection. Store credentials securely and rotate them periodically. Your adapter should request tokens and refresh them before expiry.
Right now, endpoints include getting forms and submissions. More endpoints are documented for future use. Check the API reference for updates and new capabilities.
No code is required for basic triggers and actions. The Forms API + Adafruit IO connection supports drag-and-drop mapping and predefined templates. For advanced scenarios, you can extend with custom scripts if needed.
Map fields from each form to corresponding feeds in Adafruit IO. Use data types that are supported by Adafruit IO (strings, numbers, booleans). Ensure submission_id and timestamp are captured for traceability.
Typically data is JSON and feeds accept numeric or string values. Normalize data where possible, and consider timestamps for ordering.
If you run into issues, verify credentials, test endpoints directly, and review logs. Common problems include expired tokens, insufficient permissions, and mismatched field mappings.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
