Skip to main content
Use the @bijection/connectors/trello entrypoint to declare Trello resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Cards

pull: Board cards with deleteCard withdrawal

The following example matches configuration standard.

Configuration: standard

Case: trello/cards/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: trello. Keep credential material in the private credential inventory. Inspect the complete configuration contract below for settings and conditional requirements.
Native admission analysis is available for this exact declaration. Collection: cards
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. A read-only source of one board’s cards. Nothing here creates, moves or archives a card: Trello’s card update takes no precondition, so no write is declared. The connection holds a trello credential (trello.credential). Trello needs an API key and a user token together, which it accepts as one header: Authorization: OAuth oauth_consumer_key="<key>", oauth_token="<token>". Install it as a keyword credential with scheme OAuth whose secret is the composite oauth_consumer_key="<key>", oauth_token="<token>", so neither value appears in a query string. Identity is the token’s member id from GET /1/members/me. A pass makes two reads. GET /1/boards/<board>/cards/all lists every card in one response; Trello caps a listing at 1000 results and pages only by a client-computed before/since, so the listing claims no coverage and a card absent from it is not withdrawn. closed: true is Trello’s archive: the card is published as present with closed: true. dateLastActivity is published as a value, not used as a version, because Trello does not document that every edit moves it. The second read is Trello’s own record of deletions, GET /1/boards/<board>/actions?filter=deleteCard&limit=1000, and each deleteCard action withdraws the card it names (data.card.id). The first pass reads the newest 1000; each finished pass carries the newest deletion’s date and the next pass asks since one minute before it, re-reading the boundary (a deletion published twice is the same deletion). A deletion read that returns the full 1000 is refused rather than published, because the rest is reachable only by a client-computed before and carrying past it would skip deletions. A card moved to another board stays published as it was last seen. Trello limits 300 requests per 10 seconds per key and 100 per 10 seconds per token, and answers 429 without stating a wait, so a 429 fails the pass as transient and no backoff signal is declared. Declared from Trello’s published REST reference and guides; nothing here has run against Trello or been qualified.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.