Webhook and MySQL: Deployment Event Audit Log Template

Capture every deploy-start and deploy-finish event your CI/CD pipeline fires and append it to a permanent MySQL audit table, so you always have a record of who deployed what and when.

What It Builds

A Webhook trigger receives the deployment event your pipeline posts (with fields like service, version, actor, status, and timestamp). A Connector node in Direct mode runs a single INSERT against your MySQL audit table, writing one row per event. The result is an append-only deployment log you can query for compliance, incident review, or release reporting.

The Prompt

Paste this into Miraxa and it builds the workflow, connecting the tools for you:

Build a workflow that triggers on a webhook receiving CI/CD deployment events, and for each event insert a row into my MySQL "deployment_audit" table with the service name, version, event type (deploy-start or deploy-finish), the person who triggered it, the status, and the timestamp.

Connectors Used

Webhook trigger - receives each deploy-start and deploy-finish event posted by your pipeline.
MySQL - appends one row per event to your audit table via a Direct-mode INSERT.

Customize It

Change the table name and the captured fields to match your schema (add commit_sha, environment, or duration). You can have the pipeline post to one webhook for both event types, or point each event at its own copy if you prefer separate flows.

Tips

Use the webhook's HMAC signing (Custom or GitHub mode) so only your pipeline can write to the log.
Keep the MySQL node in Direct mode for a fixed, no-AI-cost insert on every event.
Map the pipeline's timestamp into a real DATETIME column so the log sorts correctly for incident timelines.