maxinja works in steps, and consent gets a record

References

• Mention a schema, segment, contact, template or workflow in a message, and that record attaches to it. maxinja reads the real thing instead of asking you to paste it.
• Responses stream as they happen: each step, each tool call, each result, in order.

Consent, on the record

• Contact suppressions landed: unsubscribes, hard bounces, repeated soft bounces, spam complaints, and manual or legal entries.
• Every consent change writes an audit trail entry with the channel, the event, the resulting state, the opt-in level, who acted, and the context around it.
• Suppressions apply to the identifier rather than the contact, so one entry covers every record sharing that address.

Runners

• The background processors behind broadcasts, workflow runs and webhook dispatch were rebuilt to pick up unfinished work on startup.