Skip to content
Nappai Documentation

Trello Webhook

Trello Webhook is a component that listens for events from Trello and turns them into a simple message that can be used in your automation workflows. It takes the raw JSON payload sent by Trello, extracts the action type, model information, and builds a clean event object that downstream components can read.

How it Works

When Trello sends a webhook, it posts a JSON payload to the URL that Nappai exposes for this component. The component parses that payload, identifies whether the event is about a Board, List, or Card, and whether it was a create, update, or delete operation. It then packages this information into a Message object with the following fields:

  • type – “Board”, “List”, or “Card”
  • operation – “Create”, “Update”, or “Delete”
  • id – the Trello ID of the affected item
  • name – the name of the item
  • raw_event – the original JSON payload for reference

If the payload is missing or not valid JSON, the component returns an error message instead.

Inputs

Input Fields

  • Data: Use this field to quickly test the webhook component by providing a JSON payload.
  • Credential: Select the Trello Task API credential you have set up in Nappai’s credentials section.
    To use this component you must first configure the Trello Task API credential in the Credentials area of Nappai, then choose that credential in the Credential field.

Outputs

  • Event: A Message object containing the normalized event data. This output can be connected to other components such as notification senders, database writers, or custom logic blocks.

Usage Example

  1. Create a Trello Task API credential

    • Go to Nappai → Credentials → Add → Trello Task API.
    • Enter your Trello OAuth token and API key.

  2. Add the Trello Webhook component

    • Drag the component onto the canvas.
    • In the Credential field, select the credential you just created.

  3. Test with a sample payload

    {
      "action": {
        "type": "createCard",
        "data": {}
      },
      "model": {
        "id": "5f3a1c2b9e1d4c3a2b1e4f5d",
        "name": "New Card"
      }
    }

    Paste this JSON into the Data field and run the component.
    The Event output will contain:

    {
      "type": "Card",
      "operation": "Create",
      "id": "5f3a1c2b9e1d4c3a2b1e4f5d",
      "name": "New Card",
      "raw_event": { ... }
    }

  4. Connect the Event output to a notification component (e.g., Email, Slack) to alert your team whenever a card is created.

  • Webhook Receiver – A generic component that can listen to any webhook source.
  • Trello API – Allows you to query or modify Trello boards, lists, and cards directly from Nappai.
  • Message Parser – Helps extract specific fields from a Message object for further processing.

Tips and Best Practices

  • Always test the webhook with a sample payload before deploying to production.
  • Keep your Trello API key and OAuth token secure by storing them in Nappai’s credential manager.
  • Use the raw_event field if you need to debug or log the original Trello payload.
  • Combine the Trello Webhook with a filter component to trigger actions only for specific boards or lists.

Security Considerations

  • Store Trello credentials in Nappai’s secure credential store; never hard‑code them in your workflow.
  • The component does not expose the raw Trello token or key; it only uses the credential to validate the webhook.
  • Ensure that the webhook URL exposed by Nappai is protected (e.g., by IP whitelisting or a secret header) to prevent unauthorized requests.