Skip to main content
TripleBits Apprentice - Software for Agents

Menu

Sign In Register

Use Webhooks And Send-Only Integrations

Use Apprentice send-only integrations such as webhooks, Slack or Discord webhook mode, and outbound email for reports, notifications, and automation payloads.

19 views

Use Webhooks And Send-Only Integrations

Some integrations are send-only. They let an agent send information out, but they do not wake the agent from inbound messages.

Use send-only integrations for notifications, reports, status updates, and simple outbound automation.

Common Send-Only Modes

Send-only behavior can come from:

  • Webhook integrations.
  • Discord webhook mode.
  • Slack incoming webhook mode.
  • Email outbound-only configuration.
  • Other integrations configured without inbound polling or reading.

The exact options depend on the platform.

Webhook Integration

A webhook integration sends HTTP requests to an endpoint.

Configure:

  • Endpoint URL.
  • HTTP method: POST, GET, or PUT.
  • Optional Authorization header.

For GET, payload values can be merged into the URL query string. For POST or PUT, the payload is sent as JSON.

When To Use Send-Only

Use send-only integrations when the agent should:

  • Post a daily report.
  • Send a completion notification.
  • Push a structured payload to another system.
  • Notify a team without reading replies.
  • Avoid inbound wake behavior.

Agent Setup

After configuring the global integration:

  1. Open the agent's Channels tab.
  2. Subscribe the agent to the integration.
  3. Keep wake settings disabled or narrow if the platform supports inbound mode.
  4. Run a manual test.
  5. Review the sent message or webhook result.

Security Notes

Treat webhook URLs and authorization headers as credentials.

Do not paste them into prompts, chats, memory, or public docs.

Use different webhook endpoints for test and production workflows when possible.

Troubleshooting

If a webhook does not arrive, confirm the endpoint URL and method.

If the target rejects the request, check the Authorization header and expected JSON payload.

If the agent sends too often, check schedules, channel subscriptions, and prompt instructions.

If send-only notifications contain too much detail, adjust the agent prompt to produce shorter payloads.

Next Step

For bi-directional communication, configure a bot, user, or inbound-capable integration and subscribe the agent with narrow wake settings.